* [Bug libfortran/33905] show_backtrace hangs on SIGSEGV in malloc/free
[not found] <bug-33905-17017@http.gcc.gnu.org/bugzilla/>
@ 2009-03-29 9:18 ` fxcoudert at gcc dot gnu dot org
2009-03-29 13:36 ` toon at moene dot org
` (3 subsequent siblings)
4 siblings, 0 replies; 6+ messages in thread
From: fxcoudert at gcc dot gnu dot org @ 2009-03-29 9:18 UTC (permalink / raw)
To: gcc-bugs
------- 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
^ permalink raw reply [flat|nested] 6+ messages in thread* [Bug libfortran/33905] show_backtrace hangs on SIGSEGV in malloc/free
[not found] <bug-33905-17017@http.gcc.gnu.org/bugzilla/>
2009-03-29 9:18 ` fxcoudert at gcc dot gnu dot org
@ 2009-03-29 13:36 ` toon at moene dot org
2009-05-13 9:03 ` fxcoudert at gcc dot gnu dot org
` (2 subsequent siblings)
4 siblings, 0 replies; 6+ messages in thread
From: toon at moene dot org @ 2009-03-29 13:36 UTC (permalink / raw)
To: gcc-bugs
------- 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, however, from the way you implemented the traceback feature that it
is possible to hit this snag - it's just that not many people will hit it.
--
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=33905
^ permalink raw reply [flat|nested] 6+ messages in thread* [Bug libfortran/33905] show_backtrace hangs on SIGSEGV in malloc/free
[not found] <bug-33905-17017@http.gcc.gnu.org/bugzilla/>
2009-03-29 9:18 ` fxcoudert at gcc dot gnu dot org
2009-03-29 13:36 ` toon at moene dot org
@ 2009-05-13 9:03 ` fxcoudert at gcc dot gnu dot org
2009-12-17 20:17 ` pault at gcc dot gnu dot org
2009-12-17 21:59 ` toon at moene dot org
4 siblings, 0 replies; 6+ messages in thread
From: fxcoudert at gcc dot gnu dot org @ 2009-05-13 9:03 UTC (permalink / raw)
To: gcc-bugs
------- 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: people who want to
have the full power of debugging will be able to use gdb themselves. (Even with
a temporary file, other things can go wrong!)
I'd be in favour of closing this as WONTFIX, unless we have serious indication
that this actually happens often in non mixed-language cases. Toon, what's your
take?
--
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=33905
^ permalink raw reply [flat|nested] 6+ messages in thread* [Bug libfortran/33905] show_backtrace hangs on SIGSEGV in malloc/free
[not found] <bug-33905-17017@http.gcc.gnu.org/bugzilla/>
` (2 preceding siblings ...)
2009-05-13 9:03 ` fxcoudert at gcc dot gnu dot org
@ 2009-12-17 20:17 ` pault at gcc dot gnu dot org
2009-12-17 21:59 ` toon at moene dot org
4 siblings, 0 replies; 6+ messages in thread
From: pault at gcc dot gnu dot org @ 2009-12-17 20:17 UTC (permalink / raw)
To: gcc-bugs
------- 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
----------------------------------------------------------------------------
Status|UNCONFIRMED |RESOLVED
Resolution| |WONTFIX
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=33905
^ permalink raw reply [flat|nested] 6+ messages in thread* [Bug libfortran/33905] show_backtrace hangs on SIGSEGV in malloc/free
[not found] <bug-33905-17017@http.gcc.gnu.org/bugzilla/>
` (3 preceding siblings ...)
2009-12-17 20:17 ` pault at gcc dot gnu dot org
@ 2009-12-17 21:59 ` toon at moene dot org
4 siblings, 0 replies; 6+ messages in thread
From: toon at moene dot org @ 2009-12-17 21:59 UTC (permalink / raw)
To: gcc-bugs
------- 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
^ permalink raw reply [flat|nested] 6+ messages in thread