home *** CD-ROM | disk | FTP | other *** search
/ NetNews Usenet Archive 1993 #1 / NN_1993_1.iso / spool / comp / sys / apollo / 4228 < prev    next >
Encoding:
Internet Message Format  |  1993-01-12  |  947 b 
  1. Path: sparky!uunet!zaphod.mps.ohio-state.edu!howland.reston.ans.net!paladin.american.edu!gatech!destroyer!news.itd.umich.edu!pisa.citi.umich.edu!rees
  2. From: rees@pisa.citi.umich.edu (Jim Rees)
  3. Newsgroups: comp.sys.apollo
  4. Subject: Re: Apollo TRACEBACK system call
  5. Date: 12 Jan 1993 17:38:51 GMT
  6. Organization: University of Michigan CITI
  7. Lines: 9
  8. Distribution: world
  9. Message-ID: <5d8667d6.1bc5b@pisa.citi.umich.edu>
  10. References: <C0r1ws.7AB@alta-oh.com>
  11. Reply-To: Jim.Rees@umich.edu
  12. NNTP-Posting-Host: pisa.citi.umich.edu
  13.  
  14. In article <C0r1ws.7AB@alta-oh.com>, chris@zeus.alta-oh.com (Chris Murphy) writes:
  15.  
  16.   I'm looking for a system call (under 10.4) which returns
  17.   traceback information. I figure such a call must exist,
  18.   because /com/tb manages to do it somehow.
  19.  
  20. You probably want errlog_$traceback.  It will only do a traceback for the
  21. process it's running in.  If you want cross-process tracebacks, like 'tb'
  22. does, that's considerably harder.
  23.