home *** CD-ROM | disk | FTP | other *** search
- Xref: sparky vmsnet.misc:791 vmsnet.internals:1272
- Path: sparky!uunet!olivea!bu.edu!news.bbn.com!news.bbn.com!news
- From: mjensen@BBN.COM (Martin Jensen)
- Newsgroups: vmsnet.misc,vmsnet.internals
- Subject: Analyzing a process dump
- Message-ID: <lac6ibINN7h8@news.bbn.com>
- Date: 3 Sep 92 13:59:39 GMT
- Reply-To: mjensen@BBN.COM (Martin Jensen)
- Distribution: na
- Organization: Bolt Beranek and Newman Inc., Cambridge MA
- Lines: 34
- NNTP-Posting-Host: reliant.bbn.com
-
- 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???
-
- aTdHvAaNnKcSe
-
- --- Martin Jensen \ BBN Communications \ #include ---
- --- mjensen@bbn.com \ 150 CambridgePark Dr. \ <std.disclaimer> ---
- --- (617) 873-4859 \ Cambridge, MA 02140 \ ---
-