public inbox for java@gcc.gnu.org
 help / color / mirror / Atom feed
From: Bryce McKinlay <bryce@albatross.co.nz>
To: "Rolf W. Rasmussen" <rolfwr@ii.uib.no>
Cc: java-discuss@sourceware.cygnus.com
Subject: Re: Some null pointer method invocations causes segmentation fault
Date: Sat, 01 Apr 2000 00:00:00 -0000	[thread overview]
Message-ID: <38DFFC18.4BE5BF2D@albatross.co.nz> (raw)
Message-ID: <20000401000000.ZldoYFry0wTj9ywbYV13MEKe1kr1UtkDu02M0VgysYQ@z> (raw)
In-Reply-To: <20000328005223.A21555@apal.ii.uib.no>

"Rolf W. Rasmussen" wrote:

> The following program causes a segmentation fault when run, instead of
> the NullPointerException one would expect.
>
> [...]
> Program received signal SIGSEGV, Segmentation fault.
> 0x400dfef9 in java.lang.Integer.intValue (this=null)
>     at ../../../libjava/java/lang/Integer.java:60

The SIGSEGV you see in the debugger here is normal. The runtime catches
the segv and maps it into a NullPointerException. Unfortunatly, in these
cases the __throw() call in libgcc2.so is failing, which appears to be a
new regression ;-(.

Program received signal SIGABRT, Aborted.
0x40257d41 in __kill () from /lib/libc.so.6
(gdb) bt
#0  0x40257d41 in __kill () from /lib/libc.so.6
#1  0x4021b217 in raise (sig=6) at signals.c:65
#2  0x402590d8 in abort () at ../sysdeps/generic/abort.c:88
#3  0x804b59e in __default_terminate () at ../../gcc/libgcc2.c:3036
#4  0x804b5bc in __terminate () at ../../gcc/libgcc2.c:3036
#5  0x804c1fc in throw_helper (eh=@8083618, pc=@400e75ba,
my_udata=@bf7ffb0c,
    offset_p=@bf7ffb08) at ../../gcc/libgcc2.c:3170
#6  0x804c3f1 in __throw () at ../../gcc/libgcc2.c:3170
#7  0x400a98ba in Letext () at ../../../libjava/exception.cc:161
#8  0x4009f238 in catch_segv () at ../../../libjava/prims.cc:94
#9  0x400e75bb in java.lang.String.length (this=null)
    at ../../../libjava/java/lang/String.java:130
#10 0x804d97a in test.main (args=@8086ff0) at test.java:6
#11 0x40133420 in gnu::gcj::runtime::FirstThread::run (this=@8069ea0)
    at ../../../libjava/gnu/gcj/runtime/natFirstThread.cc:52
#12 0x4013e9ee in java::lang::Thread::run_ (obj=@8069ea0)
    at ../../../libjava/java/lang/natThread.cc:191
#13 0x40150821 in really_start (x=@808aff8)
    at ../../../libjava/posix-threads.cc:344
#14 0x402007aa in GC_start_routine (arg=@808bfe0)
    at ../../../boehm-gc/linux_threads.c:553
#15 0x40218b85 in pthread_start_thread (arg=@bf7ffe40) at manager.c:241


Could you enter a PR?
 http://sourceware.cygnus.com/cgi-bin/gnatsweb.pl?user=guest&password=guest&database=java&cmd=login

thanks

  [ bryce ]


  reply	other threads:[~2000-04-01  0:00 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2000-03-27 14:52 Rolf W. Rasmussen
2000-03-27 16:21 ` Bryce McKinlay [this message]
2000-03-28  1:00   ` Andrew Haley
2000-03-28 19:14     ` PR libgcj/184 [was Re: Re: Some null pointer method invocations causes segmentation fault] Bryce McKinlay
2000-03-30  3:06       ` Bryce McKinlay
2000-04-01  0:00         ` Bryce McKinlay
2000-04-01  0:00       ` Bryce McKinlay
2000-04-01  0:00     ` Some null pointer method invocations causes segmentation fault Andrew Haley
2000-04-01  0:00   ` Bryce McKinlay
2000-04-01  0:00 ` Rolf W. Rasmussen

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=38DFFC18.4BE5BF2D@albatross.co.nz \
    --to=bryce@albatross.co.nz \
    --cc=java-discuss@sourceware.cygnus.com \
    --cc=rolfwr@ii.uib.no \
    /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).