Debugging tpl code

I have a presentation teplate, which gives compilation error. How can I debug this code ?
Is there any CLT available for debugging ?
In C programming, we get tool which walks us step by step on how code is getting executed. Is there any tool available in perl for debugging ?

Find more posts tagged with

Comments

Faizi

I have a presentation teplate, which gives compilation error. How can I debug this code ?
Is there any CLT available for debugging ?
In C programming, we get tool which walks us step by step on how code is getting executed. Is there any tool available in perl for debugging ?

Perl's built-in debugger can be invoked simply by adding the -d option to your Perl command line, like below:


perl -d perlfile.pl

But in Interwoven, perl debugging perform by creating a log file in which debugging is written.
You can write debug code like below:

$DEBUG = 1;
$debugfile = "$iwhome/tmp/project/mytpl.log";
debug("^^^^^^^^^^^");
$FLAG=false;
debug($FLAG);



HTH,

Adam Stoller

Perl's built-in debugger can be invoked simply by adding the -d option to your Perl command line, like below:perl -d perlfile.pl But in Interwoven, perl debugging perform by creating a log file in which debugging is written. You can write debug code like below:
$DEBUG = 1;
$debugfile = "$iwhome/tmp/project/mytpl.log";
debug("^^^^^^^^^^^");
$FLAG=false;
debug($FLAG);
HTH,

The above assumes you've defined your own custom function called debug that "does the right thing".

For Command-line-oriented scripts - perl -d script-name is usually the way to go, or alternatively something like perl -dtkdb script-name will provide you a GUI for the debugger.

For PTs - you can "compile" the PT into a standalone Perl script using iwpt_compile's -ocode flag, but often this obscures the error you were trying to debug (IMO) and thus is only marginally helpful - except perhaps for trying to find a syntactic error. Logging information to a logfile is usually more helpful for debugging a logic error in the PT or for cross-debugging with the -ocode script in order to determine line numbering (since the line number reported in error messages generally refer to the compiled PT not the source PT code)

Ultimately, however, if you are still having problems with your PT - divide-and-conquer or remove-and-restore are your best bets. With these, you remove as much code as you can until you have something that "works" (i.e. doesn't throw an error), and then start putting back small pieces of code until it breaks again - and then debug the code you just put back. Once you have that working, you continue the process of putting back small chunks of code until eventually you have the whole PT rewritten and working (hopefully)