public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "howarth.at.gcc at gmail dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/42159] unwinding issues on darwin
Date: Tue, 31 Mar 2015 16:37:00 -0000 [thread overview]
Message-ID: <bug-42159-4-ecZRv8sSSo@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-42159-4@http.gcc.gnu.org/bugzilla/>
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.
next prev parent reply other threads:[~2015-03-31 16:19 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
[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
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
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 [this message]
2015-04-01 7:42 ` ossman at cendio dot se
2015-04-01 12:03 ` howarth.at.gcc at gmail dot com
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=bug-42159-4-ecZRv8sSSo@http.gcc.gnu.org/bugzilla/ \
--to=gcc-bugzilla@gcc.gnu.org \
--cc=gcc-bugs@gcc.gnu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).