Follow-up Comment #6, bug #24526 (project gnustep):
Unfortunately, neither file shows a backtrace of a crash.
The first file (16693) records a crash and coredump in a make process doing
some lisp/emacs stuff ... but then a gdb backtrace of something different, not
of the core image dumped.
Both files show gdb backtraces of a running process receiving a signal ...
neither shows that the process being debugged would have gone on to crash, so
it's not clear whether they demonstrate any bug at all.
Remember, that the sourcecode sample I gave shows that a signal handler has
been installed precisely to trap the case where the gcc bug causes a
segmentation fault, and recover from it. So a gdb backtrace of the point
before the signal handler is called does not demonstrate any problem.
However, it occurs to me that one way our workaround for the gcc bug could be
broken is if some other code in another thread changed the signal handler ...
there's only a small window in which that could happen, but it's possible I
suppose.
_______________________________________________________
Reply to this item at:
<http://savannah.gnu.org/bugs/?24526>
_______________________________________________
Message sent via/by Savannah
http://savannah.gnu.org/
_______________________________________________
Bug-gnustep mailing list
Bug-gnustep@gnu.org
http://lists.gnu.org/mailman/listinfo/bug-gnustep
