* [Bug target/42159] unwinding issues on darwin
[not found] <bug-42159-4@http.gcc.gnu.org/bugzilla/>
@ 2010-09-30 11:45 ` rguenth at gcc dot gnu.org
2014-04-30 9:46 ` dominiq at lps dot ens.fr
` (8 subsequent siblings)
9 siblings, 0 replies; 10+ messages in thread
From: rguenth at gcc dot gnu.org @ 2010-09-30 11:45 UTC (permalink / raw)
To: gcc-bugs
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=42159
Richard Guenther <rguenth at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Summary|[4.4/4.5/4.6] app SIGABRTs |unwinding issues on darwin
|after a trivial nested |
|throw/stack unwinding |
Known to fail| |
--- Comment #23 from Richard Guenther <rguenth at gcc dot gnu.org> 2010-09-30 10:37:10 UTC ---
I suppose this is all "user" errors which might be avoided by some more
target-os specific specs magic.
^ permalink raw reply [flat|nested] 10+ messages in thread* [Bug target/42159] unwinding issues on darwin
[not found] <bug-42159-4@http.gcc.gnu.org/bugzilla/>
2010-09-30 11:45 ` [Bug target/42159] unwinding issues on darwin rguenth at gcc dot gnu.org
@ 2014-04-30 9:46 ` dominiq at lps dot ens.fr
2014-04-30 12:42 ` michael at jarvis dot net
` (7 subsequent siblings)
9 siblings, 0 replies; 10+ messages in thread
From: dominiq at lps dot ens.fr @ 2014-04-30 9:46 UTC (permalink / raw)
To: gcc-bugs
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=42159
Dominique d'Humieres <dominiq at lps dot ens.fr> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|NEW |WAITING
--- Comment #24 from Dominique d'Humieres <dominiq at lps dot ens.fr> ---
Is this PR still present?
^ permalink raw reply [flat|nested] 10+ messages in thread* [Bug target/42159] unwinding issues on darwin
[not found] <bug-42159-4@http.gcc.gnu.org/bugzilla/>
2010-09-30 11:45 ` [Bug target/42159] unwinding issues on darwin rguenth at gcc dot gnu.org
2014-04-30 9:46 ` dominiq at lps dot ens.fr
@ 2014-04-30 12:42 ` michael at jarvis dot net
2014-04-30 13:00 ` simon at pushface dot org
` (6 subsequent siblings)
9 siblings, 0 replies; 10+ messages in thread
From: michael at jarvis dot net @ 2014-04-30 12:42 UTC (permalink / raw)
To: gcc-bugs
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=42159
--- Comment #25 from Mike Jarvis <michael at jarvis dot net> ---
The bug does not seem to be present with g++ 4.8.2 on OSX 10.9.2. I no longer
have access to a 10.6 machine, so I cannot confirm whether it is fixed with 4.8
on that system.
^ permalink raw reply [flat|nested] 10+ messages in thread* [Bug target/42159] unwinding issues on darwin
[not found] <bug-42159-4@http.gcc.gnu.org/bugzilla/>
` (2 preceding siblings ...)
2014-04-30 12:42 ` michael at jarvis dot net
@ 2014-04-30 13:00 ` simon at pushface dot org
2014-04-30 13:09 ` dominiq at lps dot ens.fr
` (5 subsequent siblings)
9 siblings, 0 replies; 10+ messages in thread
From: simon at pushface dot org @ 2014-04-30 13:00 UTC (permalink / raw)
To: gcc-bugs
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=42159
--- Comment #26 from simon at pushface dot org ---
(In reply to Dominique d'Humieres from comment #24)
> Is this PR still present?
Not with g++ (or Ada) in 4.9.0 on Max OS X 10.9.2 (darwin13.1.0).
^ permalink raw reply [flat|nested] 10+ messages in thread* [Bug target/42159] unwinding issues on darwin
[not found] <bug-42159-4@http.gcc.gnu.org/bugzilla/>
` (3 preceding siblings ...)
2014-04-30 13:00 ` simon at pushface dot org
@ 2014-04-30 13:09 ` dominiq at lps dot ens.fr
2015-03-31 15:32 ` dominiq at lps dot ens.fr
` (4 subsequent siblings)
9 siblings, 0 replies; 10+ messages in thread
From: dominiq at lps dot ens.fr @ 2014-04-30 13:09 UTC (permalink / raw)
To: gcc-bugs
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=42159
Dominique d'Humieres <dominiq at lps dot ens.fr> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|WAITING |RESOLVED
Resolution|--- |FIXED
--- Comment #27 from Dominique d'Humieres <dominiq at lps dot ens.fr> ---
> The bug does not seem to be present with g++ 4.8.2 on OSX 10.9.2.
> I no longer have access to a 10.6 machine, so I cannot confirm whether
> it is fixed with 4.8 on that system.
For the test in comment 0, I get CAUGHT on x86_64-apple-darwin10 down to 4.5.4
(with 4.4.7 the test aborts) and on powerpc-apple-darwin9 down to 4.4.7 (fink
builds).
So I am closing this PR as FIXED.
^ permalink raw reply [flat|nested] 10+ messages in thread* [Bug target/42159] unwinding issues on darwin
[not found] <bug-42159-4@http.gcc.gnu.org/bugzilla/>
` (4 preceding siblings ...)
2014-04-30 13:09 ` dominiq at lps dot ens.fr
@ 2015-03-31 15:32 ` dominiq at lps dot ens.fr
2015-03-31 16:00 ` ossman at cendio dot se
` (3 subsequent siblings)
9 siblings, 0 replies; 10+ messages in thread
From: dominiq at lps dot ens.fr @ 2015-03-31 15:32 UTC (permalink / raw)
To: gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=42159
--- Comment #29 from Dominique d'Humieres <dominiq at lps dot ens.fr> ---
> I'd like to reopen this issue as we are still seeing this with as new gcc
> as 4.8.4 (we've been unable to build anything newer). Unfortunately I do
> not seem to have the access rights to reopen the bug. Help?
I can reopen the PR, but I don't see the point:
(1) I can reproduce the problem only on x86_64-apple-darwin10 with gcc version
4.4.7
(I get 'CAUGHT' for all the other revisions I have tested on
powerpc-apple-darwin9, x86_64-apple-darwin10, and x86_64-apple-darwin14.
(2) You should be able to build 4.9 and 5.0 without any patch for
x86_64-apple-darwin* and a few for powerpc-apple-darwin9 and 5.0.
(3) Why are you not using a more recent version of OS X?
^ permalink raw reply [flat|nested] 10+ messages in thread* [Bug target/42159] unwinding issues on darwin
[not found] <bug-42159-4@http.gcc.gnu.org/bugzilla/>
` (5 preceding siblings ...)
2015-03-31 15:32 ` dominiq at lps dot ens.fr
@ 2015-03-31 16:00 ` ossman at cendio dot se
2015-03-31 16:37 ` howarth.at.gcc at gmail dot com
` (2 subsequent siblings)
9 siblings, 0 replies; 10+ messages in thread
From: ossman at cendio dot se @ 2015-03-31 16:00 UTC (permalink / raw)
To: gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=42159
--- Comment #30 from Pierre Ossman <ossman at cendio dot se> ---
(In reply to Dominique d'Humieres from comment #29)
> I can reopen the PR, but I don't see the point:
> (1) I can reproduce the problem only on x86_64-apple-darwin10 with gcc
> version 4.4.7
> (I get 'CAUGHT' for all the other revisions I have tested on
> powerpc-apple-darwin9, x86_64-apple-darwin10, and x86_64-apple-darwin14.
I'm not sure what we're doing differently in that case. Are you sure you are
using libgcc_s from your gcc and not getting the routines from libSystem? What
if you statically link libstdc++ and libgcc_eh like we do?
> (2) You should be able to build 4.9 and 5.0 without any patch for
> x86_64-apple-darwin* and a few for powerpc-apple-darwin9 and 5.0.
Sorry, my bad. It was other issues preventing us from moving our development
platform to 4.9. We should be able to do a test build. Do you think anything
has changed since 4.8.4 though?
> (3) Why are you not using a more recent version of OS X?
We need to produce binaries that most people can run, and 10.6 seemed like a
good cut-off for now. We did however see the same crashes running the binary on
10.10. We have not tested using a newer target for the gcc build though.
^ permalink raw reply [flat|nested] 10+ messages in thread* [Bug target/42159] unwinding issues on darwin
[not found] <bug-42159-4@http.gcc.gnu.org/bugzilla/>
` (6 preceding siblings ...)
2015-03-31 16:00 ` ossman at cendio dot se
@ 2015-03-31 16:37 ` howarth.at.gcc at gmail dot com
2015-04-01 7:42 ` ossman at cendio dot se
2015-04-01 12:03 ` howarth.at.gcc at gmail dot com
9 siblings, 0 replies; 10+ messages in thread
From: howarth.at.gcc at gmail dot com @ 2015-03-31 16:37 UTC (permalink / raw)
To: gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=42159
Jack Howarth <howarth.at.gcc at gmail dot com> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |howarth.at.gcc at gmail dot com
--- Comment #31 from Jack Howarth <howarth.at.gcc at gmail dot com> ---
(In reply to Pierre Ossman from comment #28)
> Or normal way of doing things is to statically link libstdc++ and libgcc_eh.
> This results in crashing programs. If we inject libSystem before libgcc_eh
> however, we get the system unwind routines and the program works fine. This
> is not quite the same as the previous cases mentioned on this bug, but the
> dumps show that a custom libgcc_s is being used so it should be equivalent.
>
You might check out the original posting on this issue...
http://lists.cs.uiuc.edu/pipermail/llvmdev/2009-September/025900.html
IMHO, the static linkage of -lgcc_eh is evil as it potentially breaks the
requirement that only a single unwinder (always the system one) be used.
^ permalink raw reply [flat|nested] 10+ messages in thread* [Bug target/42159] unwinding issues on darwin
[not found] <bug-42159-4@http.gcc.gnu.org/bugzilla/>
` (7 preceding siblings ...)
2015-03-31 16:37 ` howarth.at.gcc at gmail dot com
@ 2015-04-01 7:42 ` ossman at cendio dot se
2015-04-01 12:03 ` howarth.at.gcc at gmail dot com
9 siblings, 0 replies; 10+ messages in thread
From: ossman at cendio dot se @ 2015-04-01 7:42 UTC (permalink / raw)
To: gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=42159
--- Comment #33 from Pierre Ossman <ossman at cendio dot se> ---
Created attachment 35198
--> https://gcc.gnu.org/bugzilla/attachment.cgi?id=35198&action=edit
Remove unwinder on OS X
^ permalink raw reply [flat|nested] 10+ messages in thread* [Bug target/42159] unwinding issues on darwin
[not found] <bug-42159-4@http.gcc.gnu.org/bugzilla/>
` (8 preceding siblings ...)
2015-04-01 7:42 ` ossman at cendio dot se
@ 2015-04-01 12:03 ` howarth.at.gcc at gmail dot com
9 siblings, 0 replies; 10+ messages in thread
From: howarth.at.gcc at gmail dot com @ 2015-04-01 12:03 UTC (permalink / raw)
To: gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=42159
--- Comment #34 from Jack Howarth <howarth.at.gcc at gmail dot com> ---
(In reply to Pierre Ossman from comment #32)
> I can understand that. But in that case why keep the gcc unwinder on OS X?
Mainly inertia. The more important issue is weaning darwin off of the
compatibility unwinder which is on borrowed time and may well disappear in the
next OS release.
> If it doesn't work then including it is just an accident waiting to happen.
> I would suggest something along the lines of the attached patch.
^ permalink raw reply [flat|nested] 10+ messages in thread