Overview
Comment: | Added Perl example of using xterm for tool debug |
---|---|
Downloads: | Tarball | ZIP archive | SQL archive |
Timelines: | family | ancestors | descendants | both | v1.65-debugging-update-orig |
Files: | files | file ages | folders |
SHA1: |
342fe04d52693370d0aaaa85977602ed |
User & Date: | mrwellan on 2021-09-13 10:03:30 |
Other Links: | branch diff | manifest | tags |
Context
2021-09-13
| ||
10:12 | Added more examples check-in: 72181ffee3 user: mrwellan tags: v1.65-debugging-update-orig | |
10:03 | Added Perl example of using xterm for tool debug check-in: 342fe04d52 user: mrwellan tags: v1.65-debugging-update-orig | |
2021-09-10
| ||
15:15 | updates to debugging section in manual check-in: e347e30b71 user: mrwellan tags: v1.65-debugging-update-orig | |
Changes
Modified docs/manual/debugging.txt from [56693c04a6] to [d79a29d877].
︙ | ︙ | |||
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 ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ |
︙ | ︙ |
Modified docs/manual/megatest_manual.html from [7c63d2addb] to [c87e467a54].
︙ | ︙ | |||
2164 2165 2166 2167 2168 2169 2170 2171 2172 2173 2174 2175 2176 2177 | DEBUG [system xterm] CELLNAME [system getcellnames.sh]</pre> </div></div> <div class="paragraph"><p>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.</p></div> </div> </div> <div class="sect2"> <h3 id="_misc_other_debugging_hints">Misc Other Debugging Hints</h3> <div class="sect3"> <h4 id="_annotation_scripts_and_config_files">Annotation scripts and config files</h4> <div class="paragraph"><p>Run the "env" command to record the environment:</p></div> | > > > > > > > > > > > > > > > > > > | 2164 2165 2166 2167 2168 2169 2170 2171 2172 2173 2174 2175 2176 2177 2178 2179 2180 2181 2182 2183 2184 2185 2186 2187 2188 2189 2190 2191 2192 2193 2194 2195 | DEBUG [system xterm] CELLNAME [system getcellnames.sh]</pre> </div></div> <div class="paragraph"><p>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.</p></div> <div class="admonitionblock"> <table><tr> <td class="icon"> <img src="/nfs/pdx/disks/ice.disk.002/icfadm/pkgs/asciidoc/8.6.7/images/icons/note.png" alt="Note"> </td> <td class="content">This technique can be very helpful in debugging running of EDA tools in Perl, Ruby, Python or tcl scripts:</td> </tr></table> </div> <div class="literalblock"> <div class="title">Perl example</div> <div class="content monospaced"> <pre>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();</pre> </div></div> </div> </div> <div class="sect2"> <h3 id="_misc_other_debugging_hints">Misc Other Debugging Hints</h3> <div class="sect3"> <h4 id="_annotation_scripts_and_config_files">Annotation scripts and config files</h4> <div class="paragraph"><p>Run the "env" command to record the environment:</p></div> |
︙ | ︙ |
Modified docs/manual/megatest_manual.pdf from [06a7b4d25e] to [cc3143ceae].
cannot compute difference between binary files