public inbox for java@gcc.gnu.org
 help / color / mirror / Atom feed
From: Jack Howarth <howarth@bromo.med.uc.edu>
To: java@gcc.gnu.org, aph@redhat.com
Subject: _Unwind_FindEnclosingFunction vs darwin
Date: Fri, 18 Dec 2009 14:46:00 -0000	[thread overview]
Message-ID: <20091218144617.GA21353@bromo.med.uc.edu> (raw)

Andrew,
   As I mentioned in http://gcc.gnu.org/bugzilla/show_bug.cgi?id=41991#c36,
the darwin unwinder maintainer looked at the crash of gcj(ecj1) when compiling
java code on darwin10. He claims that the origin of the problem is the use of
the FSF unwinder extension _Unwind_FindEnclosingFunction which is not implemented
in the system unwinder on darwin10. It appears that for darwin10 and later we
will have to replace the call to _Unwind_FindEnclosingFunction on darwin with
code using dladdr() to discover if the function is known to the dynamic loader
...assuming that the use of _Unwind_FindEnclosingFunction is to tell if the code
address is static of dynamic(JIT) code.
          Jack

             reply	other threads:[~2009-12-18 14:46 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-12-18 14:46 Jack Howarth [this message]
2009-12-18 15:01 ` Andrew Haley
2009-12-18 15:54   ` Jack Howarth
2009-12-18 20:41   ` Jack Howarth
2009-12-19 10:51     ` Andrew Haley
2009-12-19 10:58       ` Bryce McKinlay
2009-12-19 11:07         ` Andrew Haley
2009-12-19 13:47       ` Jack Howarth
2009-12-19 17:26         ` Andrew Haley
2009-12-19 18:49           ` Jack Howarth
2009-12-19 19:54             ` Bryce McKinlay
2009-12-20  0:30               ` Jack Howarth
2009-12-20  2:03               ` Jack Howarth
2009-12-20 12:14                 ` Bryce McKinlay
2009-12-20 13:20                   ` Andrew Haley
2009-12-20 13:25                 ` Andrew Haley
2009-12-20 16:03                   ` Jack Howarth
2009-12-20 16:12                   ` Jack Howarth
2009-12-20 17:47                     ` Andrew Haley
2009-12-19 19:57       ` Jack Howarth
2009-12-20 13:26         ` Andrew Haley
2009-12-19  0:22   ` Jack Howarth

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=20091218144617.GA21353@bromo.med.uc.edu \
    --to=howarth@bromo.med.uc.edu \
    --cc=aph@redhat.com \
    --cc=java@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).