public inbox for java-prs@sourceware.org
help / color / mirror / Atom feed
From: "andreast at gcc dot gnu dot org" <gcc-bugzilla@gcc.gnu.org>
To: java-prs@gcc.gnu.org
Subject: [Bug java/41991] gcj segfaults on i686-apple-darwin* and x86_64-apple-darwin*
Date: Sat, 14 Nov 2009 20:57:00 -0000	[thread overview]
Message-ID: <20091114205738.26828.qmail@sourceware.org> (raw)
In-Reply-To: <bug-41991-11113@http.gcc.gnu.org/bugzilla/>



------- Comment #6 from andreast at gcc dot gnu dot org  2009-11-14 20:57 -------
I tried on another core2duo (x86_64-apple-darwin9), same issue. W/o
extra_gij_ldflags=-Wl,-allow_stack_execute for ecjx_LINK I fail with the same
entry in Library/Logs/CrashReporter:

ecj1_2009-11-14-202538_imac-catherine.crash
...

Thread 0 Crashed:
0   libSystem.B.dylib                   0x00007fff83de6f16 __kill + 10
1   libgcj.11.dylib                     0x00000001000129db _Jv_Throw + 75
(exception.cc:128)
2   libgcj.11.dylib                     0x00000001000050fd __ZL10catch_segvi +
61
3   libSystem.B.dylib                   0x00007fff83de53fa _sigtramp + 26
4   ???                                 0x0000000103f057a0 0 + 4361050016

Thread 1:
0   libSystem.B.dylib                   0x00007fff83d86dc2 __semwait_signal +
10
1   libgcj.11.dylib                     0x0000000100060bd4
_Jv_CondWait(_Jv_ConditionVariable_t*, _Jv_Mutex_t*, long long, int) + 404
...

Adding '-Wl,-allow_stack_execute' to the ecjx_LINK stage, I can build _and_
execute the resulting class (with gij) and the resulting binary w/o
CrashReporter call.

Also, I removed the '-Wl,-allow_stack_execute' invocation in
testsuite/lib/libjava.exp and ran the testsuite. I then found exactly the same
pattern as from the above pattern from CrashReporter for several test cases.

>From my POV, the failure has nothing todo with unwinder issues.

I'd like to know what CPU you're running the build/install/test on.
Is your extra_gij_ldflags equal to '-Wl,-allow_stack_execute'?
Do you clean the install directory before installing a new version?

And yes, it is not gcj which fails but ecj.


-- 


http://gcc.gnu.org/bugzilla/show_bug.cgi?id=41991


  parent reply	other threads:[~2009-11-14 20:57 UTC|newest]

Thread overview: 55+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-11-09  0:24 [Bug java/41991] New: " 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 [this message]
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
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

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=20091114205738.26828.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).