Date: Sat, 06 Nov 1999 10:12:50 -0600 From: Patrick Hartling <patrick@137.org> To: freebsd-current@freebsd.org Subject: Java segfaulting Message-ID: <19991106161250.A17A05D12@friley-162-229.res.iastate.edu>
next in thread | raw e-mail | index | archive | help
I'm running -current as of 9:00 CDT October 30, and ever since I rebuilt, I
have not been able to run any Java applications. All of them exit with
the following error output:
SIGSEGV 11* segmentation violation
Full thread dump:
Monitor Cache Dump:
Registered Monitor Dump:
Monitor IO lock: <unowned>
Child death monitor: <unowned>
Event monitor: <unowned>
I/O monitor: <unowned>
Alarm monitor: <unowned>
Memory allocation lock: <unowned>
Monitor registry: <unowned>
Thread Alarm Q:
I also get this on the console:
pid 649 (java_X), uid 13773: exited on signal 6
Is anyone else seeing this? If not, is there anything I might have missed
when updating last weekend? My previous build was from October 12 (cvsup'd
around 4:00 CDT I believe). I do know for sure that Java worked during the
time between rebuilds.
-Patrick
Patrick L. Hartling | Research Assistant, VRAC
patrick@137.org | 2624 Howe Hall -- (515)294-4916
http://www.137.org/patrick/ | http://www.vrac.iastate.edu/
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?19991106161250.A17A05D12>