George <greerga@CIRCLEMUD.ORG> writes:
> >Has anyone had any experience with getting a clean core file using
> >abort() (or any other piece of crashing code) inside a SEGV handler?
> [...]
> >#0 segvsig (sig=11) at comm.c:1751
> >#1 0xbfffc5d4 in ?? ()
>
> Could have been corrupted by the crash. Try using this in the segv
> handler if you have GCC:
>
> fprintf(stderr, "%p\n", __builtin_return_address(0));
>
> Then see how that compares to #1. (Although it might be a good idea to use
> something other than fprintf...)
Wasn't corrupted. "kill -SEGV `pidof threads`" produced the same
effect for some reason.
--
James Turner chip.turner@vanderbilt.edu UIN: 1102038
http://www.vuse.vanderbilt.edu/~turnerjh/
+------------------------------------------------------------+
| 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