Date: Tue, 26 Feb 2002 19:32:24 +0100 From: "Koster, K.J." <K.J.Koster@kpn.com> To: "FreeBSD Java mailing list (E-mail)" <freebsd-java@freebsd.org> Subject: 1.3.1p6 dies sigbus with threads Message-ID: <59063B5B4D98D311BC0D0001FA7E452205FDA3A4@l04.research.kpn.com>
next in thread | raw e-mail | index | archive | help
Dear All, and Bill Huey in particular, :)
I can make 1.3.1p6 fall onto it's face by creating threads and having them
generate HTTP traffic against a local web server (HTTPUnit against an Orion
server). The code works fine on a FreeBSD machine with Linux-jdk13 and on
the massive Sun that will be our production server.
However, in the interest of testing our native port I have been running the
same test in our native port on a spare box. It does not hold as well. I'm
rerunning the tests with java_g instead of java but I won't stick around for
the results tonight.
The test loads the box past comfortable memory allocation. It's swapping and
generally not having a fun time with this. It's a 64MB box, 200MHz cpu. 128
threads make it die occasionally.
nobby% gdb -core java.core
/usr/local/jdk1.3.1/jre/bin/i386/green_threads/java
GNU gdb 4.18
Copyright 1998 Free Software Foundation, Inc.
GDB is free software, covered by the GNU General Public License, and you are
welcome to change it and/or distribute copies of it under certain
conditions.
Type "show copying" to see the conditions.
There is absolutely no warranty for GDB. Type "show warranty" for details.
This GDB was configured as "i386-unknown-freebsd"...(no debugging symbols
found)...
Core was generated by `java'.
Program terminated with signal 6, Abort trap.
Reading symbols from
/usr/local/jdk1.3.1/jre/lib/i386/green_threads/libhpi.so...(no debugging
symbols found)...done.
Reading symbols from /usr/lib/libc.so.4...(no debugging symbols
found)...done.
Reading symbols from /usr/lib/libm.so.2...(no debugging symbols
found)...done.
Reading symbols from
/usr/local/jdk1.3.1/jre/lib/i386/classic/libjvm.so...(no debugging symbols
found)...done.
Reading symbols from /usr/local/jdk1.3.1/jre/lib/i386/libverify.so...(no
debugging symbols found)...done.
Reading symbols from /usr/local/jdk1.3.1/jre/lib/i386/libjava.so...(no
debugging symbols found)...done.
Reading symbols from /usr/local/jdk1.3.1/jre/lib/i386/libzip.so...(no
debugging symbols found)...done.
Reading symbols from /usr/local/jdk1.3.1/jre/lib/i386/libnet.so...(no
debugging symbols found)...done.
Reading symbols from /usr/libexec/ld-elf.so.1...(no debugging symbols
found)...done.
#0 0x280b6994 in kill () from /usr/lib/libc.so.4
(gdb) bt
#0 0x280b6994 in kill () from /usr/lib/libc.so.4
#1 0x280f2b35 in abort () from /usr/lib/libc.so.4
#2 0x28160ad9 in Abort () from
/usr/local/jdk1.3.1/jre/lib/i386/classic/libjvm.so
#3 0x28189a9f in panicHandler () from
/usr/local/jdk1.3.1/jre/lib/i386/classic/libjvm.so
#4 0x28076647 in userSignalHandler () from
/usr/local/jdk1.3.1/jre/lib/i386/green_threads/libhpi.so
#5 0x28076600 in intrDispatch () from
/usr/local/jdk1.3.1/jre/lib/i386/green_threads/libhpi.so
#6 0x2806f917 in intrDispatchMD () from
/usr/local/jdk1.3.1/jre/lib/i386/green_threads/libhpi.so
#7 0xbfbfffac in ?? ()
#8 0x2815a7d5 in cacheAlloc () from
/usr/local/jdk1.3.1/jre/lib/i386/classic/libjvm.so
#9 0x2815abe9 in allocArray () from
/usr/local/jdk1.3.1/jre/lib/i386/classic/libjvm.so
#10 0x28190e4f in N1_newarray6 () from
/usr/local/jdk1.3.1/jre/lib/i386/classic/libjvm.so
#11 0x28e7c7e8 in ?? ()
#12 0x8052400 in ?? ()
#13 0x0 in ?? ()
(gdb)
I would appreciate suggestions on how to debug this in more detail.
How can I enable additional debugging code that can help track this bug
down?
Kees Jan
=====================================================
You can't have everything. Where would you put it?
[Steven Wright]
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-java" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?59063B5B4D98D311BC0D0001FA7E452205FDA3A4>