How to debug tcl script files?

[Altera_Forum]

I have searched for information on how to debug tcl script files for Quartus, but found none! 

 Background: Some tcl script files generated by sopc builder such as those from DDR2 instantiations "altmemddr_0_pin_assignments.tcl", did not function as I expected. So I thought there ougth to be some tools to assist.   Can it be true that there is not a debug tool or method?    Consider the complexity of some of those files (see for instance "altmemddr_0_phy_ddr_pins.tcl" generated by the DDR2 wizard)!   How do you solve this problem in your workflow?

[Altera_Forum]

--- Quote Start ---  I have searched for information on how to debug tcl script files for Quartus, but found none!   Background: Some tcl script files generated by sopc builder such as those from DDR2 instantiations "altmemddr_0_pin_assignments.tcl", did not function as I expected. So I thought there ougth to be some tools to assist.   Can it be true that there is not a debug tool or method?    Consider the complexity of some of those files (see for instance "altmemddr_0_phy_ddr_pins.tcl" generated by the DDR2 wizard)!   How do you solve this problem in your workflow?  --- Quote End ---    Hi Larsen,  as far as I know there is no debugger for TCL available. But what is your problem. Is a syntax error reported ??? Did the controller did not run ???  Kind regards  GPK

[Altera_Forum]

I think the premise behind the scripts is that they just work, and you're not supposed to debug them. That being said, I've done it myself the old fashioned way, adding puts statements to get the info I need. I'd prefer if they had a debug variable that dumped a lot more info, and I think, emphasis on think, the scripts are being improved to be more readable.