It sounds really like you're trying to reinvent the wheel - a core
dumb already gives you all of this information (the function,
filename, and line number of the statement that caused the crash).
Why not just use the core dump instead? You could probably even write
a few lines into 'autorun' to automatically extract that info from the
core every time the MUD crashes.
BTW, "RETSIGTYPE" isn't really a type of function, just a macro name
that I pulled out of the air so that autoconf (the "configure" script)
can tell comm.c what the return type of signal() is (either void, or
int, or a pointer to the former signal handling function).
Akuma/Chris Baggett/DOOMer writes:
>RETSIGTYPE mysignal(yadda, SIGSEG) //segmentation fault
>{
>log("SegFault from %s, %s (%d)", __FILE__, __FUNCTION__, __LINE__);
>}
>i know that wouldn't work too well, (i think i've tried and gotten
>mysignal() as the function).
>i was wondering if possibly there's a __PREVFILE__ or __PREVFUNCTION__
>or something like that?
>thanks.
+------------------------------------------------------------+
| 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/08/00 PST