🚀 go-pugleaf

In article <lac6ibINN7h8@news.bbn.com>, mjensen@BBN.COM (Martin Jensen) writes:
> Greetings again vms.wizards ...
> 
>     One more question, then I promise I'll leave you alone ... for a
>     while anyway :-)
> 
>     I've got an executable that runs with the /dump qualifier.  I expect
>     that, on occasion, the process will crash.  (as a matter of fact, we
>     intentionally crash it if software detects an unrecoverable condition
>     in the code).
> 
>     The problem is that the dump files are pretty useless.  'show  calls'
>     reports  only the module names - no routine names - and I've only got
>     access to universal symbols.  The program is compiled with the /debug
>     switch and linked with /trace.
> 
>     If  I  link  with  /debug,  I get the debugger linked in.  I've tried
>     linking with /debug=foo (where foo contains  the  program  main)  ...
>     that  seems  to  work  (outside  of  some strange symbol behavior for
>     objects in foo), but now I've got the overhead  of  the  DST  in  the
>     runtime image.
> 
>     Ideally, I would like to be able use anal/proc/image=xxx against the
>     dump from the normally linked executable - where xxx would be an
>     image containing the full DST and GST.  The couple of options I have
>     tried allow me to analyze the dump, but the symbol locations don't
>     match properly between the images.
> 
>     Any ideas???
> 
> 
> ---   Martin Jensen     \   BBN Communications     \  #include          ---
>  ---   mjensen@bbn.com   \   150 CambridgePark Dr.  \  <std.disclaimer>  ---
>   ---   (617) 873-4859    \   Cambridge, MA   02140  \                    ---



ANA/PROCESS has a /IMAGE qualifer.  One option you have, assuming you want
to keep two copies, which is sometime advantageous, is when building the 
image perform two links:  One with DEBUG and one w/out.  The non-debug
version can always be executed as the production version.  The /DEBUG
version is specified as the image to use for obtaining the symbols when
examining the dump via the /IMAGE= qualifier.  (Obviously you will want to
name the DEBUG image w/ a different file name or extension). This does, of 
course, eat up more disk space but leaves you with a version that can be used 
for debugging w/out having to rebuild from - possibly modified - sources.

*+*+*+*+*+*+*+*+*+*+*+*+*+*+*+*+*+*+*+*+*+*+*+*+*+*+*+*+*+*+*+*+*+*+*+*+*+*+*+*
Ed Heinrich
The LOKI Group, Inc.
HEINRICH@yvax.byu.EDU
*+*+*+*+*+*+*+*+*+*+*+*+*+*+*+*+*+*+*+*+*+*+*+*+*+*+*+*+*+*+*+*+*+*+*+*+*+*+*+*