Overview
Comment: | updates to debugging section in manual |
---|---|
Downloads: | Tarball | ZIP archive | SQL archive |
Timelines: | family | ancestors | descendants | both | v1.65-debugging-update-orig |
Files: | files | file ages | folders |
SHA1: |
e347e30b71c2fe7b245fa1b812b8df02 |
User & Date: | mrwellan on 2021-09-10 15:15:47 |
Other Links: | branch diff | manifest | tags |
Context
2021-09-13
| ||
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 | |
12:54 | More tweaks to debugging section check-in: 44a6aef391 user: mrwellan tags: v1.65-debugging-update-orig | |
Changes
Modified docs/manual/debugging.txt from [3b7237dbd3] to [56693c04a6].
︙ | ︙ | |||
229 230 231 232 233 234 235 | 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. | > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > | 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 255 256 257 258 259 260 261 262 263 264 265 266 267 268 269 270 271 272 273 274 275 276 277 278 | 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 ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ Run the "env" command to record the environment: env | sort > stagename.log In a config file: .megatest.config, runconfigs.config and testconfig ................... #{shell env | sort > stagename.log} # or [system env | sort > stagename.log} ................... In scripts just insert the command: .myscript.sh .............................. env > somefile.log .............................. Start an xterm to examine the environment, run scripts etc: In a config file: .megatest.config, runconfigs.config and testconfig files .............................. #{shell xterm} (this blocks) or #{shell xterm &} (this is non-blocking) .............................. Similarly in a script just call the xterm. |
Modified docs/manual/megatest_manual.html from [df309572de] to [7c63d2addb].
︙ | ︙ | |||
2165 2166 2167 2168 2169 2170 2171 2172 2173 2174 2175 2176 2177 2178 | 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> </div> <div class="sect1"> <h2 id="_how_to_do_things">How To Do Things</h2> <div class="sectionbody"> <div class="sect2"> | > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > | 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 2196 2197 2198 2199 2200 2201 2202 2203 2204 2205 2206 2207 2208 2209 2210 2211 2212 2213 2214 | 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> <div class="paragraph"><p>env | sort > stagename.log</p></div> <div class="paragraph"><p>In a config file:</p></div> <div class="literalblock"> <div class="title">megatest.config, runconfigs.config and testconfig</div> <div class="content monospaced"> <pre>#{shell env | sort > stagename.log} # or [system env | sort > stagename.log}</pre> </div></div> <div class="paragraph"><p>In scripts just insert the command:</p></div> <div class="literalblock"> <div class="title">myscript.sh</div> <div class="content monospaced"> <pre>env > somefile.log</pre> </div></div> <div class="paragraph"><p>Start an xterm to examine the environment, run scripts etc:</p></div> <div class="paragraph"><p>In a config file:</p></div> <div class="literalblock"> <div class="title">megatest.config, runconfigs.config and testconfig files</div> <div class="content monospaced"> <pre>#{shell xterm} (this blocks) or #{shell xterm &} (this is non-blocking)</pre> </div></div> <div class="paragraph"><p>Similarly in a script just call the xterm.</p></div> </div> </div> </div> </div> <div class="sect1"> <h2 id="_how_to_do_things">How To Do Things</h2> <div class="sectionbody"> <div class="sect2"> |
︙ | ︙ |
Modified docs/manual/megatest_manual.pdf from [ffe67439cb] to [06a7b4d25e].
cannot compute difference between binary files
Modified docs/megatest-debug-tutorial.odp from [3f635392f7] to [2cdb7efb2f].
cannot compute difference between binary files