home *** CD-ROM | disk | FTP | other *** search
- Xref: sparky comp.sources.wanted:4265 comp.unix.questions:10850 comp.windows.x:16390
- Path: sparky!uunet!wupost!zaphod.mps.ohio-state.edu!rphroy!kocrsv01!c23st
- From: c23st@kocrsv01.delcoelect.com (Spiros Triantafyllopoulos)
- Newsgroups: comp.sources.wanted,comp.unix.questions,comp.windows.x
- Subject: Stack Traceback program wanted
- Message-ID: <1992Sep9.143656.20352@kocrsv01.delcoelect.com>
- Date: 9 Sep 92 14:36:56 GMT
- Sender: news@kocrsv01.delcoelect.com (Usenet News Account)
- Organization: Delco Electronics Corp.
- Lines: 36
-
-
- Hello net,
-
- we're looking for a program to do stack a trace before it coredumps. We
- would like to see, for example, the sequences of calls that resulted
- in the program to bomb.
-
- many years back, we wrote something like this for VMS, using PL/1 and
- it proved invaluable in helping us debug highly complex software. When
- the program would bomb, we'd get a stack trace like:
-
- Main:
- foo( )
- bar( )
- abnormal termination line so and so.
-
- Now we're doing lots of X windows stuff and once in a while we dump
- core and would like some hint as to why this happens. This should not be
- impossible as 'trace' does more or less what we want. We have our own
- signal catcher (signal 11, where are you?) and at least do some damage
- repair there but would very much like more information.
-
- So it looks like I'm after 'trace' that can be linked in user programs
- and provide us with the information above. Environment's strictly Unix,
- SunOS and HP-UX.
-
- Any hints on how to do this would be vastly appreciated...
-
- Thanks in advance,
-
- Spiros
-
- --
- Spiros Triantafyllopoulos c23st@kocrsv01.delcoelect.com
- Software Technology, Delco Electronics striantafyll@kosds1.gm.hac.com
- GM Hughes Electronics, Kokomo, IN 46904 [A Different Kind of Disclaimer]
-