[Bug libfortran/33905] show_backtrace hangs on SIGSEGV in malloc/free

2011-05-17 Thread burnus at gcc dot gnu.org
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=33905 Tobias Burnus burnus at gcc dot gnu.org changed: What|Removed |Added CC||burnus at gcc

[Bug libfortran/33905] show_backtrace hangs on SIGSEGV in malloc/free

2009-12-17 Thread pault at gcc dot gnu dot org
--- Comment #4 from pault at gcc dot gnu dot org 2009-12-17 20:17 --- I think that FX was right, since Toon has not responded in 6 months. Entering a WONTFIX Paul -- pault at gcc dot gnu dot org changed: What|Removed |Added

[Bug libfortran/33905] show_backtrace hangs on SIGSEGV in malloc/free

2009-12-17 Thread toon at moene dot org
--- Comment #5 from toon at moene dot org 2009-12-17 21:58 --- (Even with a temporary file, other things can go wrong!) Paul, you are right - I agree with FX, but forgot to reply. Closing as WONTFIX is OK with me. -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=33905

[Bug libfortran/33905] show_backtrace hangs on SIGSEGV in malloc/free

2009-05-13 Thread fxcoudert at gcc dot gnu dot org
--- Comment #3 from fxcoudert at gcc dot gnu dot org 2009-05-13 09:03 --- Frankly, this is a snag in a non-default debugging feature in rare conditions; that has to be a third-order enhancement request, at least! :) We cannot provide completely foolproof debugging capablities anyway:

[Bug libfortran/33905] show_backtrace hangs on SIGSEGV in malloc/free

2009-03-29 Thread fxcoudert at gcc dot gnu dot org
--- Comment #1 from fxcoudert at gcc dot gnu dot org 2009-03-29 09:18 --- Toon, do you have an example that shows this happening? -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=33905

[Bug libfortran/33905] show_backtrace hangs on SIGSEGV in malloc/free

2009-03-29 Thread toon at moene dot org
--- Comment #2 from toon at moene dot org 2009-03-29 13:36 --- I'll try to come up with a bug report this week (the original case is much to complicated to use as an example). However, it might take some time and it also might be system dependent to trigger this event. It's clear,