Operating System - HP-UX
1833861 Members
1881 Online
110063 Solutions
New Discussion

Re: SIGSEGV 11* segmentation violation

 
Basem Garada
New Member

SIGSEGV 11* segmentation violation

Hi,
Can someone explain, why and how to solve this error I got.
This ends with a core dump.
----
102518820 Mar 19 16:17 core
-----
Below is the full log..

SIGSEGV 11* segmentation violation
si_signo [11]: SIGSEGV 11* segmentation violation
si_errno [0]: Error 0
si_code [0]: SEGV_UNKNOWN [addr: 0x417c0000]

stackpointer=7f7f1608

Full thread dump Classic VM (1.3.1.02-JPSE_1.3.1.02_20011206, native threads):
"JIT Compiler" (TID:0x775374e0, sys_thread_t:0x401a8738, state:CW, native ID
:0x6) prio=2
"Finalizer" (TID:0x77537520, sys_thread_t:0x401a5778, state:CW, native ID:0x
5) prio=8
at java.lang.Object.wait(Native Method)
at java.lang.ref.ReferenceQueue.remove(Unknown Source)
at java.lang.ref.ReferenceQueue.remove(Unknown Source)
at java.lang.ref.Finalizer$FinalizerThread.run(Finalizer.java:162)
"Reference Handler" (TID:0x775372f8, sys_thread_t:0x401a3330, state:CW, nati
ve ID:0x4) prio=10
at java.lang.Object.wait(Native Method)
at java.lang.Object.wait(Unknown Source)
at java.lang.ref.Reference$ReferenceHandler.run(Unknown Source)
"Signal dispatcher" (TID:0x77537328, sys_thread_t:0x401a1390, state:CW, nati
ve ID:0x3) prio=5
"main" (TID:0x775371a8, sys_thread_t:0x40123ed0, state:R, native ID:0x1) pri
o=5
Monitor Cache Dump:
java.lang.ref.Reference$Lock@77537308/77606938:
Waiting to be notified:
"Reference Handler" (0x401a3330)
java.lang.ref.ReferenceQueue$Lock@77537538/77606E18:
Waiting to be notified:
"Finalizer" (0x401a5778)
Registered Monitor Dump:
JIT thread lock:
Waiting to be notified:
"JIT Compiler" (0x401a8738)
utf8 hash table:
JNI pinning lock 31:
JNI pinning lock 30:
JNI pinning lock 29:
JNI pinning lock 28:
JNI pinning lock 27:
JNI pinning lock 26:
JNI pinning lock 25:
JNI pinning lock 24:
JNI pinning lock 23:
JNI pinning lock 22:
JNI pinning lock 21:
JNI pinning lock 20:
JNI pinning lock 19:
JNI pinning lock 18:
JNI pinning lock 17:
JNI pinning lock 16:
JNI pinning lock 15:
JNI pinning lock 14:
JNI pinning lock 13:
JNI pinning lock 12:
JNI pinning lock 11:
JNI pinning lock 10:
JNI pinning lock 9:
JNI pinning lock 8:
JNI pinning lock 7:
JNI pinning lock 6:
JNI pinning lock 5:
JNI pinning lock 4:
JNI pinning lock 3:
JNI pinning lock 2:
JNI pinning lock 1:
JNI pinning lock 0:
JNI global reference lock:
BinClass lock:
Class linking lock:
System class loader lock:
Code rewrite lock:
Heap lock:
Monitor cache lock: owner "main" (0x40123ed0) 1 entry
Thread queue lock: owner "main" (0x40123ed0) 1 entry
Monitor registry: owner "main" (0x40123ed0) 1 entry

Abort(coredump)

Any suggestions ??

Thanks

Basem
3 REPLIES 3
Basem Garada
New Member

Re: SIGSEGV 11* segmentation violation

I forget to add this:

HP-UX B.11.11 U 9000/889

java version "1.3.1.02"
Java(TM) 2 Runtime Environment, Standard Edition (build 1.3.1.02-011206-02:17)
Java HotSpot(TM) Server VM (build 1.3.1 1.3.1.02-JPSE_1.3.1.02_20011206 PA2.0, mixed mode)

SHLIB_PATH=:/opt/java1.3/jre/lib:/opt/java1.3/jre/lib/PA_RISC2.0/classic:/opt/java1.3/jre/lib/PA_RISC2.0


Java out-of-box had been installed.

Also alll patches required for Java SDK 1.3 along with their dependencies had been installed.

Do I need to tune the JVM..??

Let me know if any more info is required
Clemens van Everdingen
Honored Contributor

Re: SIGSEGV 11* segmentation violation

Hi,

My guess is to set your LANG variable to C.iso88591

It has something to do with this.

take a look at the /etc/rc.config.d/LANG file), HP-UX and java defaults to using HP-Roman8 as its default font. In most cases, this is not an issue, but java is a bit of a different case. Most systems default to using iso8859.1 as its default font. In order for HP-UX to use this font, it needs to set LANG=C.iso88591

Good luck,
The computer is a great invention, there are as many mistakes as ever, but they are nobody's fault !
Basem Garada
New Member

Re: SIGSEGV 11* segmentation violation

I had made the change in LANG and set it to
LANG=C.iso88591

Still I got the same error.

Do I need to set other variables, or should I adjust kernel parameters..