This is the mail archive of the java@gcc.gnu.org mailing list for the Java project.

Index Nav:	[Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav:	[Date Prev] [Date Next]	[Thread Prev] [Thread Next]
Other format:	[Raw text]

Re: Question about POSIX libgcj signals / exception handling

From: Andrew Haley <aph at redhat dot com>
To: Andrew Pinski <pinskia at physics dot uc dot edu>
Cc: David Daney <ddaney at avtrex dot com>, gnustuff at thisiscool dot com, java at gcc dot gnu dot org
Date: Mon, 13 Mar 2006 12:17:58 +0000
Subject: Re: Question about POSIX libgcj signals / exception handling
References: <URC8D9GFKFBA0KF94DBGOWT3YDCIC.441257fc@d9300> <4412695A.4070007@avtrex.com> <f65929b5f9fde49b73fcd561ad3aa8d5@physics.uc.edu>

Andrew Pinski writes:
 > 
 > On Mar 11, 2006, at 1:08 AM, David Daney wrote:
 > 
 > > SIGSEGV gets converted to NullPointerException.  This is unconditional 
 > > it happens even if the faulting location is far away from address 
 > > zero.      Native code is not treated any differently than the java 
 > > code. Any SIGSEGV is converted to NPE.
 > 
 > This is not true for the PPC OS X implementation.  Only null pointer 
 > accesses are
 > converted to NPEs.

In that case, I guess we can't use SIGSEGV handlers to handle NPEs.
Unfortunate, but it should still work OK.

Andrew.

References:
- Question about POSIX libgcj signals / exception handling
  - From: Mohan Embar
- Re: Question about POSIX libgcj signals / exception handling
  - From: David Daney
- Re: Question about POSIX libgcj signals / exception handling
  - From: Andrew Pinski

Index Nav:	[Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav:	[Date Prev] [Date Next]	[Thread Prev] [Thread Next]