Ulrich Drepper <drepper(a)cygnus.com> writes in xemacs-beta(a)xemacs.org:
SL Baur <steve(a)xemacs.org> writes:
> I don't know about that. There used to be code in XEmacs to
> self-generate a C stack backtrace in Solaris. I took it out because
> it had a tendency to crash in the middle of printing the backtrace.
The code I have in glibc does not have this problem. There are
three
functions:
...
I would say that seeing these functions crashing is highly unlikely
unless the memory the libc uses gets clobbered.
That's a very likely possibility.
It is not a simple minded implementation.
I was not suggesting it was, nor was I referring at all to your
implementation, but rather to how I've seen XEmacs behave when it is
about to go down in flames. XEmacs does quite a lot when a fatal
error occurs and it is not uncommon that a second fatal error occurs
when it is trying to clean up from the first one. In general I want
to aim towards simplifying the fatal error code because as you point
out, no matter how carefully you code, you can still be defeated if
your memory gets clobbered.