public inbox for java-patches@gcc.gnu.org
 help / color / mirror / Atom feed
From: "gaurav.rustagi" <gaurav.rustagi85@gmail.com>
To: java-patches@gcc.gnu.org
Subject: Re: Fix 64-bit PR16923 on Solaris 10+/x86
Date: Tue, 08 Jan 2013 11:41:00 -0000	[thread overview]
Message-ID: <1357645281971-902934.post@n5.nabble.com> (raw)
In-Reply-To: <yddmxnfp9o2.fsf@manam.CeBiTec.Uni-Bielefeld.DE>

Hi,

I am having a similar issue here. Please read the following.

I am getting a crash when a native exception through JNI is propagated to
Java. The source code is really simple and it just throws a native
exception. I think the process crashes when it tries to unwind the stack
after an exception is thrown. You can see the error below. One more thing,
it only happens when the native library is compiled on 64 bit arch, and it
does work successfully on 32 bit arch. I am using gcc compiler and stats are
mentioned below as well. Let me know if you need more information. One more
thing, this code works perfectly well in Linux systems and i could see one
compiler option "--disable-libunwind-exceptions" on Linux. Does this option
really play any role for these kind of exceptions ? Should we put this
option whiling building gcc compiler on Solaris box ? 

uname: SunOS
uname -m: i86pc

compiler info
Using built-in specs.
COLLECT_GCC=g++
COLLECT_LTO_WRAPPER=/export/home/gcc4/bin/../libexec/gcc/i386-pc-solaris2.10/4.6.3/lto-wrapper
Target: i386-pc-solaris2.10
Configured with: ../gcc-4.6.3/configure --prefix=/usr/local/gcc4
--enable-__cxa_atexit
Thread model: posix
gcc version 4.6.3 (GCC)


From Crash Report:
Stack: [0xfffffd7fffbff000,0xfffffd7fffe00000), sp=0xfffffd7fffdfe4d8, free
space=2045k
Native frames: (J=compiled Java code, j=interpreted, Vv=VM code, C=native
code)
C 0x00000000000129f5
C [libc.so.1+0xe08b9] _Unwind_RaiseException+0x46
C [libstdc++.so.6.0.16+0xf4a79] __cxa_throw+0x59
C [libtestjni.so+0x1d92] Java_testJava_TEST+0xca
j testJava.TEST()I+0
j testJava.main([Ljava/lang/StringV+14
v ~StubRoutines::call_stub
V [libjvm.so+0x401398]
V [libjvm.so+0x401618]
V [libjvm.so+0x4018dd]
V [libjvm.so+0x4e6414]
V [libjvm.so+0x4ef694]
C [java+0x3169] main+0x649
C [java+0x29cc] _PROCEDURE_LINKAGE_TABLE_+0x3e4

library dependencies :
SERVER:/$HOME/simpleJNITest$ldd libtestjni.so
libstdc++.so.6 => /usr/local/gcc4/lib/amd64/libstdc++.so.6
libm.so.2 => /lib/64/libm.so.2
libgcc_s.so.1 => /usr/local/gcc4/lib/amd64/libgcc_s.so.1
libc.so.1 => /lib/64/libc.so.1



--
View this message in context: http://gcc.1065356.n5.nabble.com/Fix-64-bit-PR16923-on-Solaris-10-x86-tp774103p902934.html
Sent from the gcc - java - patches mailing list archive at Nabble.com.

  reply	other threads:[~2013-01-08 11:41 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-01-05 17:01 Rainer Orth
2013-01-08 11:41 ` gaurav.rustagi [this message]
2013-01-08 13:37   ` Andrew Haley
2013-01-10  8:33     ` gaurav.rustagi
2013-01-10  9:56       ` Andrew Haley

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=1357645281971-902934.post@n5.nabble.com \
    --to=gaurav.rustagi85@gmail.com \
    --cc=java-patches@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).