229
230
231
232
233
234
235
236
237
238
239
240
241
242
|
CELLNAME [system getcellnames.sh]
-----------------
When this test is run an xterm will pop up. In that xterm the
environment is exactly that in which the script "getcellnames.sh"
would run. You can now debug the script to find out why it isn't
working as expected.
Misc Other Debugging Hints
~~~~~~~~~~~~~~~~~~~~~~~~~~
Annotation scripts and config files
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
|
>
>
>
>
>
>
>
>
>
>
>
>
|
229
230
231
232
233
234
235
236
237
238
239
240
241
242
243
244
245
246
247
248
249
250
251
252
253
254
|
CELLNAME [system getcellnames.sh]
-----------------
When this test is run an xterm will pop up. In that xterm the
environment is exactly that in which the script "getcellnames.sh"
would run. You can now debug the script to find out why it isn't
working as expected.
NOTE: This technique can be very helpful in debugging running of EDA tools in Perl, Ruby, Python or tcl scripts:
.Perl example
..............................
some_code();
$cmdline="virtuoso -some-switches and params ...";
print "$cmdline"; # print the command line so you can paste it into the xterm that pops up
system("xterm"); # this line is added for the debug and removed when done
system($cmdline);
more_code();
..............................
Misc Other Debugging Hints
~~~~~~~~~~~~~~~~~~~~~~~~~~
Annotation scripts and config files
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
|