home *** CD-ROM | disk | FTP | other *** search
- Xref: sparky vmsnet.misc:797 vmsnet.internals:1284
- Path: sparky!uunet!mitech!gjc
- From: gjc@mitech.com (George J. Carrette)
- Newsgroups: vmsnet.misc,vmsnet.internals
- Subject: Re: Analyzing a process dump
- Message-ID: <2612@mitech.com>
- Date: 4 Sep 92 15:28:18 GMT
- References: <lac6ibINN7h8@news.bbn.com>
- Distribution: na
- Organization: Mitech Corporation, Concord MA
- Lines: 16
-
- In article <lac6ibINN7h8@news.bbn.com>, mjensen@BBN.COM (Martin Jensen) writes:
- > If I link with /debug, I get the debugger linked in. I've tried ...
-
- This should be a FAQ item. Maybe it is already.
-
- The trick people use is to LINK/DEBUG and then use a command
- procedure that calls VMS PATCH to change the image back to thinking
- it was LINK/NODEBUG.
-
- That way you get all the symbols in the image without having it start
- up in the debugger.
-
- You can get a SETDEBUG.C or NSETDEBUG.COM, or other various of that
- from various places. Probably VMSNET.SOURCES archives.
-
- -gjc
-