On linux ia64 the build of libawt starting at b39 references libmlib_image.so
instead of libmlib_image_g.so. Because libmlib_image.so references libjvm.so
in a jvmg run both libjvm.so and libjvm_g.so are brought into the same
process. These causes strange failures because you get sort of a mismash
of global state and the jvm gets confused.

If you run the testcase for 5025935 you will see this failure:

   # To suppress the following error report, specify this argument
   # after -XX: or in .hotspotrc: SuppressErrorAt=/heap.cpp:137]
   #
   # An unexpected error has been detected by HotSpot Virtual Machine:
   #
   # Internal Error (/BUILD_AREA/jdk1.5.0/hotspot/src/share/vm/memory/heap.cpp,
137), pid=15577, tid=6151
   #
   # Java VM: Java HotSpot(TM) 64-Bit Server VM (1.5.0-beta2-b48-debug mixed mode)
   #
   # Error: assert(length *_segment_size >= sizeof(FreeBlock),"not enough room
for FreeList")
   # An error report file with more information is saved as hs_err_pid15577.log
   #

running any build from b39 on. b38 works fine. Here is the ldd output
for the two builds.

b38:

ldd /java/re/j2se/1.5/promoted/all/b38/binaries/linux-ia64/jre/lib/ia64/libawt_g.so
        libmlib_image_g.so => not found
        libjvm_g.so => not found
        libm.so.6.1 => /lib/libm.so.6.1 (0x200000000039c000)
        libdl.so.2 => /lib/libdl.so.2 (0x2000000000438000)
        libjava_g.so => not found
        libc.so.6.1 => /lib/libc.so.6.1 (0x2000000000450000)
        /lib/ld-linux-ia64.so.2 => /lib/ld-linux-ia64.so.2 (0x2000000800000000)

b39:
ldd /java/re/j2se/1.5/promoted/all/b39/binaries/linux-ia64/jre/lib/ia64/libawt_g.so
        libmlib_image.so => not found
        libjvm_g.so => not found
        libm.so.6.1 => /lib/libm.so.6.1 (0x200000000039c000)
        libdl.so.2 => /lib/libdl.so.2 (0x2000000000438000)
        libjava.so => not found
        libc.so.6.1 => /lib/libc.so.6.1 (0x2000000000450000)
        /lib/ld-linux-ia64.so.2 => /lib/ld-linux-ia64.so.2 (0x2000000800000000)