abort()ing inside segv handler

From: James Turner (turnerjh@XTN.NET)
Date: 06/30/98

Has anyone had any experience with getting a clean core file using
abort() (or any other piece of crashing code) inside a SEGV handler?
It works fine with mine except that the stack frame has one bad entry
-- the entry right before the segv is messed up... ie, the function
that made the mud crash.  Quite annoying.  Thoughts?  I know Erwin has
done some work on this... any suggestions would be great.  A trivial
segv handler results in the same effect, so it's not anything
happening in the handler itself.  Here's a sample backtrace fwiw:

#0  segvsig (sig=11) at comm.c:1751
#1  0xbfffc5d4 in ?? ()
#2  0x8099c54 in command_interpreter (ch=0x8332fe8, argument=0xbfffd664 "zonein") at interpreter.c:622
#3  0x80a7a56 in game_loop (mother_desc=3) at comm.c:568
#4  0x80a6744 in init_game (port=5000) at comm.c:213
#5  0x80a6694 in main (argc=3, argv=0xbffffad4) at comm.c:180

The useful information is gone :\

James Turner                chip.turner@vanderbilt.edu   UIN: 1102038

     | Ensure that you have read the CircleMUD Mailing List FAQ:  |
     | http://democracy.queensu.ca/~fletcher/Circle/list-faq.html |

This archive was generated by hypermail 2b30 : 12/15/00 PST