public inbox for java-patches@gcc.gnu.org
 help / color / mirror / Atom feed
From: Andrew Haley <aph@redhat.com>
To: "gaurav.rustagi" <gaurav.rustagi85@gmail.com>
Cc: java-patches@gcc.gnu.org
Subject: Re: Fix 64-bit PR16923 on Solaris 10+/x86
Date: Tue, 08 Jan 2013 13:37:00 -0000	[thread overview]
Message-ID: <50EC20F2.1060803@redhat.com> (raw)
In-Reply-To: <1357645281971-902934.post@n5.nabble.com>

Hi,

On 01/08/2013 11:41 AM, gaurav.rustagi wrote:
> 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 ? 

It's a bug in the unwinder in your libc.  You should try calling backtrace
from a segfault handler written in C.  This will tell you if the problem
is anything to do with libjava.

Andrew.

  reply	other threads:[~2013-01-08 13:37 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
2013-01-08 13:37   ` Andrew Haley [this message]
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=50EC20F2.1060803@redhat.com \
    --to=aph@redhat.com \
    --cc=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).