home *** CD-ROM | disk | FTP | other *** search
- Newsgroups: comp.os.vms
- Path: sparky!uunet!gatech!rpi!usc!cs.utexas.edu!geraldo.cc.utexas.edu!slcs.slb.com!BRYDON@128.58.42.3
- From: brydon@asl.slb.com (Harvey Brydon (918)250-4312)
- Subject: Re: Misbehaving calling functions in C
- Message-ID: <1993Jan12.131544.17026@slcs.slb.com>
- Sender: news@slcs.slb.com (News Administrator)
- Nntp-Posting-Host: 129.87.186.2
- Reply-To: brydon@dsn.SINet.slb.com
- Organization: Schlumberger/Anadrill Sugar Land, TX
- References: <726762256snz@spliff.demon.co.uk>
- Date: Tue, 12 Jan 93 13:15:44 GMT
- Lines: 24
-
- In article <726762256snz@spliff.demon.co.uk>, journeyman@spliff.demon.co.uk
- (Andy Settle) writes:
- >I'm maintaining an old application (written in VAXC) which runs
- >asynch/ASTs. *Somewhere* there is a function calling a routine
- >with garbage parameters - this is easy to trap. The problem is
- >that it's proving difficult to track down the caller. Is there an
- >way of viewing the call stack without stopping the image? Using
- >the debugger is not possible as the called routine is called from
- >*everywhere* (it's actually an audit trail log routine).
- >
- >One idea is LIB$SIGNAL(SS$_DEBUG, "SHOW CALLS"). Any other
- >suggestions? My last site had a nice piece of macro which could
- >generate a process dump file without exiting the process but i
- >didn't manage to get a copy before i left.
-
- Once again, in Fortran:
-
- call lib$signal(%val('98198'X))
-
- HTH
- _______________________________________________________________
- Harvey Brydon | Internet: brydon@dsn.SINet.slb.com
- Dowell Schlumberger | P.O.T.S.: (918)250-4312
- If 'pro' is the opposite of 'con', what is the opposite of 'progress'?
-