home *** CD-ROM | disk | FTP | other *** search
- Newsgroups: vmsnet.internals
- Path: sparky!uunet!europa.asd.contel.com!paladin.american.edu!darwin.sura.net!spool.mu.edu!umn.edu!umeecs!emunix.emich.edu!pampreen
- From: pampreen@emunix.emich.edu (Dave Pampreen)
- Subject: Re: Use of $PUTMSG system service
- Message-ID: <1992Dec31.185446.20862@zip.eecs.umich.edu>
- Followup-To: This #897
- Sender: Dave A. Pampreen pampreen@emunix.emich.edu
- Organization: Eastern Michigan University
- References: <74*/S=dip115/OU=cc/O=uib/PRMD=iris/ADMD=mensatex/C=es/@MHS>
- Distribution: You the reader.
- Date: Thu, 31 Dec 1992 18:54:46 GMT
- Lines: 23
-
- In article Jaime C. Jansenwirth <dip115@cc.uib.es> writes:
- > Hi, everybody!
- [stuff deleted]
- > I know that is an easy way to print a message with LIB$SIGNAL, but I do
- >not want to print the symbolic stack traceback each time an error occurs.
- >
- >***** I wish you a Happy New Year 1993 ! *****
- >
- Happy new year to you too.
-
- If you don't want the trace back information to be displayed, when you
- compile and link it, don't use the traceback feature. I do believe this
- is what you want to do:
- $ macro/debug=notraceback [your.dir]your.file
- $ link/notrace [your.dir]your.obj
-
- Then you will not see any traceback info.
-
- Dave Pampreen - Supervising Consultant - Goddard Lab Learning Technologies.
- Eastern Michigan University - pampreen@emunix.emich.edu
-
-
-
-