libgcj/1171: Some null pointer method invocations cause SIGABRT

libgcj/1171: Some null pointer method invocations cause SIGABRT

[rolfwr]

>Number:         1171
>Category:       libgcj
>Synopsis:       Some null pointer method invocations cause SIGABRT
>Confidential:   no
>Severity:       serious
>Priority:       medium
>Responsible:    tromey
>State:          closed
>Class:          sw-bug
>Submitter-Id:   net
>Arrival-Date:   Wed Dec 20 12:16:50 PST 2000
>Closed-Date:    Mon Jun 05 22:23:25 PDT 2000
>Last-Modified:  Mon Jun  5 22:30:00 PDT 2000
>Originator:     Rolf W. Rasmussen <rolfwr@ii.uib.no>
>Release:        gcc version 2.96 20000327 (experimental)
>Organization:
>Environment:
i586-pc-linux-gnu (Debian)
>Description:
Some methods when invoced using a null pointer, will generate
a SIGABRT, instead of the NullPointerException one would
expect.

The problem seems only to occur with simple methods such as
Integer.intValue(), String.length(), Vector.size().
>How-To-Repeat:
Compile and run

--------
public class NullPointerExceptionTest {
    public static void main(String[] args) {
        ((Integer) null).intValue();
    }
}
--------

Other one-liners that trigger the same problem:
    ((String) null).length();
    ((java.util.Vector) null).size();
    Boolean ref = null; ref.booleanValue();
>Fix:

>Release-Note:

>Audit-Trail:

Formerly PR libgcj/184


From: bryce@sourceware.cygnus.com
To: java-gnats@sourceware.cygnus.com
Cc:  
Subject: libgcj/184
Date: 29 Mar 2000 02:09:00 -0000

 CVSROOT:	/cvs/java
 Module name:	libgcj
 Changes by:	bryce@sourceware.cygnus.com	00/03/28 18:09:00
 
 Modified files:
 	libjava/testsuite: ChangeLog 
 Added files:
 	libjava/testsuite/libjava.lang: pr184.out pr184.java 
 
 Log message:
 	Test case for PR libgcj/184:
 	* libjava.lang/pr184.java: New file.
 	* libjava.lang/pr184.out: New file.
 
 Patches:
 http://gcc.gnu.org/cgi-bin/gcc/libjava/testsuite/ChangeLog.diff?cvsroot=java&r1=1.79&r2=1.80
 http://gcc.gnu.org/cgi-bin/gcc/libjava/testsuite/libjava.lang/pr184.out.diff?cvsroot=java&r1=NONE&r2=1.1
 http://gcc.gnu.org/cgi-bin/gcc/libjava/testsuite/libjava.lang/pr184.java.diff?cvsroot=java&r1=NONE&r2=1.1
 
Responsible-Changed-From-To: apbianco->tromey
Responsible-Changed-By: tromey
Responsible-Changed-When: Thu Apr 27 17:19:45 2000
Responsible-Changed-Why:
    I fixed it.
State-Changed-From-To: open->feedback
State-Changed-By: tromey
State-Changed-When: Thu Apr 27 17:19:45 2000
State-Changed-Why:
    I've checked in a patch to fix this problem.
    Can you try it and get back to me?
    If not, tell me and I will just close this PR.
    Thanks.

From: tromey@cygnus.com
To: apbianco@cygnus.com, java-gnats@sourceware.cygnus.com, rolfwr@ii.uib.no,
  tromey@cygnus.com
Cc:  
Subject: Re: libgcj/184
Date: 28 Apr 2000 00:19:45 -0000

 Synopsis: Some null pointer method invocations cause SIGABRT
 
 Responsible-Changed-From-To: apbianco->tromey
 Responsible-Changed-By: tromey
 Responsible-Changed-When: Thu Apr 27 17:19:45 2000
 Responsible-Changed-Why:
     I fixed it.
 State-Changed-From-To: open->feedback
 State-Changed-By: tromey
 State-Changed-When: Thu Apr 27 17:19:45 2000
 State-Changed-Why:
     I've checked in a patch to fix this problem.
     Can you try it and get back to me?
     If not, tell me and I will just close this PR.
     Thanks.
 
 http://sourceware.cygnus.com/cgi-bin/gnatsweb.pl?cmd=view&pr=184&database=java
State-Changed-From-To: feedback->closed
State-Changed-By: bryce
State-Changed-When: Mon Jun  5 22:23:25 2000
State-Changed-Why:
    FIXED. The PR 2 compiler fix, combined with the PR 218 runtime patch have resolved this issue.
    I have verified that all these test cases now throw NullPointerExceptions correctly.

From: bryce@albatross.co.nz
To: java-gnats@sourceware.cygnus.com, rolfwr@ii.uib.no, tromey@cygnus.com
Cc:  
Subject: Re: libgcj/184
Date: 6 Jun 2000 05:23:25 -0000

 Synopsis: Some null pointer method invocations cause SIGABRT
 
 State-Changed-From-To: feedback->closed
 State-Changed-By: bryce
 State-Changed-When: Mon Jun  5 22:23:25 2000
 State-Changed-Why:
     FIXED. The PR 2 compiler fix, combined with the PR 218 runtime patch have resolved this issue.
     I have verified that all these test cases now throw NullPointerExceptions correctly.
 
 http://sourceware.cygnus.com/cgi-bin/gnatsweb.pl?cmd=view&pr=184&database=java
>Unformatted: