home *** CD-ROM | disk | FTP | other *** search
- Path: sparky!uunet!crdgw1!rpi!gatech!paladin.american.edu!howland.reston.ans.net!spool.mu.edu!sdd.hp.com!decwrl!pa.dec.com!engage.pko.dec.com!nntpd.lkg.dec.com!gauche.zko.dec.com!jnelson
- From: jnelson@gauche.zko.dec.com (Jeff E. Nelson)
- Newsgroups: comp.os.vms
- Subject: Re: forcing Traceback output
- Message-ID: <1993Jan27.234409.13431@nntpd.lkg.dec.com>
- Date: 27 Jan 93 23:44:09 GMT
- References: <86657@ut-emx.uucp>
- Sender: usenet@nntpd.lkg.dec.com (USENET News System)
- Reply-To: jnelson@gauche.zko.dec.com (Jeff E. Nelson)
- Organization: Digital Equipment Corporation
- Lines: 33
-
-
- In article <86657@ut-emx.uucp>, pso@phobos.as.utexas.edu (P Samuel
- Odoms) writes:
- |>Is there a way to force the traceback handler to get control, at any
- |>time during the execution of an image, to print out the current stack
- |>information? I should add that I'm hoping there is something
- |>analogous to LIB$SIGNAL(SS$_DEBUG). I don't want my image to
- |>abort execution, though; it should be able to resume where it left off.
-
- Yes, this is possible if the following conditions are met:
-
- 1. The program calls lib$signal with an -informational- message. You'll have
- to invent your own, since there isn't a default one available. Inventing
- your own is a good idea anyway, since you can inform your user that what
- follows is expected, e.g.,
-
- %FOOBAR-I-TRACEBACK, forcing a traceback now
-
- 2. The program's exception handlers (if any) must RESIGNAL this informational
- message. If any exception handler handles the exception, then
- traceback will never get a chance to see it.
-
- 3. The program is compiled with the default switch of /DEBUG=TRACEBACK.
-
- 4. The program is linked with the default switch of /TRACE.
-
- 5. The program is not run with /DEBUG. TRACE can't be activated if the debugger
- is already running.
-
-
- -Jeff E. Nelson
- -Digital Equipment Corporation
- -Internet: jnelson@gauche.zko.dec.com
-