I'm consistently getting things like:
SIGSEGV 11* segmentation violation
stackpointer=0xbfffd97c
Full thread dump Classic VM (Linux_JDK_1.2_pre-release-v2, native threads):
"Finalizer" (TID:0x40ce3320, sys_thread_t:0x80ccb88, state:CW, native ID:0xc04)
prio=8
at java.lang.Object.wait(Native Method)
at java.lang.ref.ReferenceQueue.remove(ReferenceQueue.java:112)
at java.lang.ref.ReferenceQueue.remove(ReferenceQueue.java:127)
at java.lang.ref.Finalizer$FinalizerThread.run(Finalizer.java:174)
"Reference Handler" (TID:0x40ce33b0, sys_thread_t:0x80c83d0, state:CW, native
ID:0x803) prio=10
at java.lang.Object.wait(Native Method)
at java.lang.Object.wait(Object.java:424)
at java.lang.ref.Reference$ReferenceHandler.run(Reference.java:114)
"SIGQUIT handler" (TID:0x40ce33e0, sys_thread_t:0x80c0e68, state:R, native
ID:0x402) prio=5
"main" (TID:0x40ce31e0, sys_thread_t:0x804c570, state:R, native ID:0x400) prio=5
at java.lang.String.<init>(Compiled Code)
at java.io.DataInputStream.readUTF(Compiled Code)
at java.io.DataInputStream.readUTF(Compiled Code)
at sun.tools.java.BinaryConstantPool.<init>(Compiled Code)
at sun.tools.java.BinaryClass.load(Compiled Code)
at sun.tools.javac.BatchEnvironment.loadFile(Compiled Code)
at sun.tools.javac.BatchEnvironment.loadDefinition(Compiled Code)
at sun.tools.javac.Main.compile(Compiled Code)
at sun.tools.javac.Main.main(Compiled Code)
Monitor Cache Dump:
java.lang.ref.Reference$Lock@40CE33C0/40E7EF10: owner "main" (0x804c570) 1 entry
Waiting to be notified:
"Reference Handler" (0x80c83d0)
sun.tools.javac.Main@40CEDB88/40EC6888: owner "main" (0x804c570) 1 entry
java.lang.ref.ReferenceQueue$Lock@40CE3338/40E7F3E0: <unowned>
Waiting to be notified:
"Finalizer" (0x80ccb88)
Registered Monitor Dump:
PCMap lock: <unowned>
utf8 hash table: <unowned>
JNI pinning lock: <unowned>
JNI global reference lock: owner "main" (0x804c570) 1 entry
BinClass lock: owner "main" (0x804c570) 1 entry
Class linking lock: owner "main" (0x804c570) 1 entry
System class loader lock: <unowned>
Code rewrite lock: <unowned>
Heap lock: owner "main" (0x804c570) 1 entry
Monitor cache lock: owner "main" (0x804c570) 2 entries
Thread queue lock: owner "main" (0x804c570) 2 entries
Monitor registry: owner "main" (0x804c570) 1 entry
This happens with large compiles (intensive, actually, i.e. "make -j 4
jar" or "-j 8" for a medium-sized java project) )using JDK 1.2 version
2 for Linux. I'm a bit concerned, because this primarily seems to be
happening on 2 machines which are a bit difference from what I'm
usually using. Could this be related to the compiler/JDK, or (as I'm
suspecting) related to hardware problems (in particular, memory/ram)?
Thoughts and opinions on this matter are very welcome!
best,
-tony
--
-- We just moved to Harborview. Note change in CFAR phone numbers! --
--
A.J. Rossini Research Assistant Professor of Biostatistics
Center for AIDS Research/HMC Biostatistics/Univ. of Washington
Box 359931 Box 357232
206-731-3647 (3693=fax) 206-543-1044 (3286=fax)
[EMAIL PROTECTED] [EMAIL PROTECTED]
http://www.biostat.washington.edu/~rossini/
----------------------------------------------------------------------
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
