public inbox for java-prs@sourceware.org
help / color / mirror / Atom feed
From: "howarth at nitro dot med dot uc dot edu" <gcc-bugzilla@gcc.gnu.org>
To: java-prs@gcc.gnu.org
Subject: [Bug java/41991] gcj segfaults on i686-apple-darwin9 and x86_64-apple-darwin9
Date: Wed, 11 Aug 2010 13:42:00 -0000 [thread overview]
Message-ID: <20100811134224.3950.qmail@sourceware.org> (raw)
In-Reply-To: <bug-41991-11113@http.gcc.gnu.org/bugzilla/>
------- Comment #47 from howarth at nitro dot med dot uc dot edu 2010-08-11 13:42 -------
Also from a the darwin unwinder maintainer...
> I took a look at the bug report you made. Right off, I can tell that
> the problem is that _Unwind_FindEnclosingFunction() is not
> implemented. Well, it is implemented as a not_implemented macro...
> It is an FSF extension and has some semantics that can't be supported.
...
> _Unwind_Find_FDE is implemented on 10.6.
>
> The general issue is that on 10.6 and later the dwarf unwind info may
> not exist. It may be replaced (by the linker tool) with compact
> unwind info. So any function that assumes FDEs exist may not work.
This is the reason that the _Unwind_FindEnclosingFunction() call is
re-exported
under a different name in libgcc_ext. This call requires _Unwind_Find_FDE and
has been replaced with a not_implemented macro which silently aborts. A radar
is open to have the gross use of not_implemented macros replaced with a check
if -no-compact-unwind is in use. In that case, the compatibility unwinder in
libSystem (which supports FDEs) would be in use and those calls could be made
functional again.
Note that this all stems from the fact that darwin10 has the compact unwind
code generation as the default.
--
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=41991
next prev parent reply other threads:[~2010-08-11 13:42 UTC|newest]
Thread overview: 60+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-11-09 0:24 [Bug java/41991] New: gcj segfaults on i686-apple-darwin* and x86_64-apple-darwin* howarth at nitro dot med dot uc dot edu
2009-11-09 0:44 ` [Bug java/41991] " howarth at nitro dot med dot uc dot edu
2009-11-09 0:45 ` howarth at nitro dot med dot uc dot edu
2009-11-11 22:40 ` andreast at gcc dot gnu dot org
2009-11-12 2:43 ` howarth at nitro dot med dot uc dot edu
2009-11-13 14:26 ` howarth at nitro dot med dot uc dot edu
2009-11-14 20:57 ` andreast at gcc dot gnu dot org
2009-11-15 1:57 ` howarth at nitro dot med dot uc dot edu
2009-11-15 19:20 ` howarth at nitro dot med dot uc dot edu
2009-11-15 22:52 ` howarth at nitro dot med dot uc dot edu
2009-11-16 1:26 ` howarth at nitro dot med dot uc dot edu
2009-11-17 0:37 ` howarth at nitro dot med dot uc dot edu
2009-11-17 0:39 ` howarth at nitro dot med dot uc dot edu
2009-11-18 1:04 ` howarth at nitro dot med dot uc dot edu
2009-11-18 1:19 ` howarth at nitro dot med dot uc dot edu
2009-11-18 1:39 ` howarth at nitro dot med dot uc dot edu
2009-11-18 14:02 ` howarth at nitro dot med dot uc dot edu
2009-11-19 21:15 ` andreast at gcc dot gnu dot org
2009-11-27 21:28 ` howarth at nitro dot med dot uc dot edu
2009-11-27 21:38 ` howarth at nitro dot med dot uc dot edu
2009-11-28 20:14 ` andreast at gcc dot gnu dot org
2009-11-28 20:25 ` howarth at nitro dot med dot uc dot edu
2009-11-28 20:27 ` andreast at gcc dot gnu dot org
2009-11-28 20:32 ` howarth at nitro dot med dot uc dot edu
2009-11-28 23:01 ` howarth at nitro dot med dot uc dot edu
2009-11-29 7:41 ` howarth at nitro dot med dot uc dot edu
2009-11-29 7:48 ` howarth at nitro dot med dot uc dot edu
2009-12-01 4:56 ` howarth at nitro dot med dot uc dot edu
2009-12-03 15:33 ` howarth at nitro dot med dot uc dot edu
2009-12-05 7:03 ` howarth at nitro dot med dot uc dot edu
2009-12-05 8:21 ` howarth at nitro dot med dot uc dot edu
2009-12-05 8:54 ` howarth at nitro dot med dot uc dot edu
2009-12-05 9:02 ` howarth at nitro dot med dot uc dot edu
2009-12-09 18:45 ` bryce at gcc dot gnu dot org
2009-12-09 18:46 ` bryce at gcc dot gnu dot org
2009-12-10 14:32 ` howarth at nitro dot med dot uc dot edu
2009-12-17 23:30 ` howarth at nitro dot med dot uc dot edu
2009-12-18 14:54 ` howarth at nitro dot med dot uc dot edu
2009-12-19 0:35 ` howarth at nitro dot med dot uc dot edu
2010-02-02 8:18 ` andreast at gcc dot gnu dot org
2010-02-02 8:19 ` andreast at gcc dot gnu dot org
2010-02-02 8:19 ` andreast at gcc dot gnu dot org
2010-02-03 3:33 ` [Bug java/41991] gcj segfaults on i686-apple-darwin9 and x86_64-apple-darwin9 howarth at nitro dot med dot uc dot edu
2010-06-20 6:57 ` gcc at ryandesign dot com
2010-08-11 12:32 ` iains at gcc dot gnu dot org
2010-08-11 12:50 ` andreast at gcc dot gnu dot org
2010-08-11 13:14 ` howarth at nitro dot med dot uc dot edu
2010-08-11 13:42 ` howarth at nitro dot med dot uc dot edu [this message]
2010-08-11 15:23 ` howarth at nitro dot med dot uc dot edu
2010-08-17 13:13 ` iains at gcc dot gnu dot org
2010-08-21 0:31 ` howarth at nitro dot med dot uc dot edu
2010-08-21 0:55 ` howarth at nitro dot med dot uc dot edu
2010-08-21 2:24 ` howarth at nitro dot med dot uc dot edu
2010-08-22 4:56 ` howarth at nitro dot med dot uc dot edu
2010-08-23 16:32 ` howarth at nitro dot med dot uc dot edu
[not found] <bug-41991-8172@http.gcc.gnu.org/bugzilla/>
2013-09-14 12:01 ` iains at gcc dot gnu.org
2014-02-16 13:15 ` jackie.rosen at hushmail dot com
2014-11-03 19:44 ` fxcoudert at gcc dot gnu.org
2021-02-28 15:36 ` egallager at gcc dot gnu.org
2023-05-16 19:14 ` iains at gcc dot gnu.org
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=20100811134224.3950.qmail@sourceware.org \
--to=gcc-bugzilla@gcc.gnu.org \
--cc=java-prs@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).