home *** CD-ROM | disk | FTP | other *** search
- Path: sparky!uunet!olivea!decwrl!pa.dec.com!nntpd2.cxo.dec.com!nntpd.lkg.dec.com!gauche.zko.dec.com!jnelson
- From: jnelson@gauche.zko.dec.com (Jeff E. Nelson)
- Newsgroups: vmsnet.internals
- Subject: Re: How can I determine if running under debugger?
- Message-ID: <1992Jul27.211743.16665@nntpd.lkg.dec.com>
- Date: 27 Jul 92 21:17:43 GMT
- References: <MARBY.92Jul24152309@laura.harvard.edu> <1992Jul27.133619.28409@nntphost.ciba-geigy.ch>
- Sender: usenet@nntpd.lkg.dec.com (USENET News System)
- Reply-To: jnelson@gauche.zko.dec.com (Jeff E. Nelson)
- Organization: Digital Equipment Corporation
- Lines: 20
-
-
- In article <1992Jul27.133619.28409@nntphost.ciba-geigy.ch>,
- bnebga@ciba-geigy.ch (Gary Nebbett) writes:
- |>The debugger modifies certain entries in the system service dispatch
- |>table.
-
- Not always, and we aren't the only ones to do this. This is really not a
- dependable way to figure out if the debugger is active. Jeff Diewald's
- suggestion of walking the image list to look for an image named "DEBUG"
- is the best option I can think of.
-
- Of course, you'll have to decide how close you want to monitor this
- information: just because the debugger isn't active when the program checks
- doesn't mean that it can't be activated later: the user can type CTRL/Y
- DEBUG at any time.
-
- -Jeff Nelson
- -DEBUG developer
- -Digital Equipment Corporation
- -Internet: jnelson@gauche.zko.dec.com
-