dlopen("libgnomevfs-2.so.0") will cause jvm crash on Redhat AS4 when the java application exits. It can reproduce always using mustang b53+ on Redhat AS4.

If we replaced the client/libjvm.so of b53 , it worked.
So it might be hotspot's problem on linux.
See 6336247 for details.

To reproduce the problem, compile and run the following T.java with mustang b53+.
import java.awt.*;
public class T
{
  public static void main(String[] args){
   System.out.println(Desktop.getDesktop().isDesktopSupported(); //dlopen libgnomevfs-2.so
  }
}

Jvm will crash after running "java T" .

The printed stack trace shows it crashed at libc's exit() function:

#
# An unexpected error has been detected by HotSpot Virtual Machine:
#
# SIGSEGV (0xb) at pc=0x00001e62, pid=13223, tid=3051248560
#
# Java VM: Java HotSpot(TM) Client VM (1.6.0-ea-b55 mixed mode, sharing)
# Problematic frame:
# C 0x00001e62
...
Stack: [0xb5d65000,0xb5de6000), sp=0xb5de4d5c, free space=511k
Native frames: (J=compiled Java code, j=interpreted, Vv=VM code, C=native code)
C 0x00001e62 ---> It's "_fini() in exit()" using java -XX:OnError="pstack %p"
C [librt.so+0x6dd6]
C [ld-linux.so.2+0xc887]
C [libc.so.6+0x2a467] exit+0x77
V [libjvm.so+0x372bfd]
V [libjvm.so+0x372117]
V [libjvm.so+0x3718fc]
V [libjvm.so+0x371abf]
V [libjvm.so+0x3716ff]
V [libjvm.so+0x2ccdb3]
C [libpthread.so.0+0x5341]

VM_Operation (0xb533f740): exit, mode: safepoint, requested by thread 0x08481a00
...