🚀 go-pugleaf

>>>>> "Mark" == Mark Rosenstein <mbr@bellcore.com> writes:

	Mark> I have an application that is killed (I assume by the
	Mark> OS). I wanted to try and figure out what was going on
	Mark> using the casevision debugger.  I was unable to figure
	Mark> out a way to catch the kill, and when the program
	Mark> mysteriously dies, all I get in the debugger is process
	Mark> xxxx: terminated.

	Mark> Is there a way to catch the kill signal with the
	Mark> casevision debugger?  With other signals (like INT) when
	Mark> set it in the signal panel, and then send the
	Mark> application (attached process) an INT, it happily
	Mark> catches it.  And I can look at the stack, etc, etc.

	Mark> When I set SIGKILL in the signal panel, and then send
	Mark> kill -9 xxxx, the process just terminates. [This also
	Mark> happens when the OS does it to me].

	Mark> Have I missed something?

Sounds like your application is leaking memory, and is running out of
swap space. Check your console window if this is what is happening.

If so, you should link your application with libmalloc_cv.a and turn
on malloc/free tracing in the Performance Panel. Then bring up Heap
View and see where you are leaking memory. If you need help, let me
know. 

kittu..

--
-------
Krishna Kolluri		1L-545		kittu@sgi.com
Silicon Graphics, Inc.			Off:(415)390-1859