home *** CD-ROM | disk | FTP | other *** search
- Path: sparky!uunet!charon.amdahl.com!pacbell.com!decwrl!olivea!charnel!rat!usc!sdd.hp.com!saimiri.primate.wisc.edu!ames!agate!spool.mu.edu!uwm.edu!linac!unixhub!stanford.edu!leland.Stanford.EDU!dhinds
- From: dhinds@leland.Stanford.EDU (David Hinds)
- Newsgroups: comp.sys.sgi
- Subject: Re: Killed?
- Message-ID: <1992Nov4.203129.29035@leland.Stanford.EDU>
- Date: 4 Nov 92 20:31:29 GMT
- References: <1992Nov4.065527.4867@shannon.ee.wits.ac.za>
- Sender: news@leland.Stanford.EDU (Mr News)
- Organization: DSG, Stanford University, CA 94305, USA
- Lines: 17
-
- In article <1992Nov4.065527.4867@shannon.ee.wits.ac.za> philip@concave.cs.wits.ac.za (Philip Machanick) writes:
- >Occasionally when I have a bug in a program or allocate a very large
- >data structure, my program dies with the message
- > Killed.
- >This is not enourmously informative (whatever happened to core dumps)?
- >
- >What's going on?
-
- I think this is what happens when a process exceeds the stack size
- resource limit. The reason there is no core dump is that when the
- stack is full, there is no way to call the regular signal handler.
- You should get an error message in the SYSLOG, though. You might be
- able to get around this by using the sigstack() call to specify an
- alternate stack for signal handlers; this requires -D_BSD_SIGNALS.
-
- - David Hinds
- dhinds@allegro.stanford.edu
-