On 09.05.2012 21:55, Hubert Zhang wrote:
Running on linux and libvirt 0.9.11. Using libvirt java 0.4.7.
Notice
that the Tomcat server crashes and shows the dump like this:
*** glibc detected *** jsvc.exec: double free or corruption (out):
0x086f14a8 ***
======= Backtrace: =========
/lib/libc.so.6[0xc03745]
/lib/libc.so.6(cfree+0x59)[0xc03b89]
/tmp/jna/jna486823639517928939.tmp(Java_com_sun_jna_Native_free+0x1d)[0x430c4c]
[0xb46de240]
[0xb46d218d]
[0xb46d218d]
[0xb46d218d]
[0xb46cf3e6]
/usr/lib/jvm/sun-java-6u24/jre/lib/i386/server/libjvm.so[0x13bdb21]
/usr/lib/jvm/sun-java-6u24/jre/lib/i386/server/libjvm.so[0x15b3478]
/usr/lib/jvm/sun-java-6u24/jre/lib/i386/server/libjvm.so[0x13bd94f]
/usr/lib/jvm/sun-java-6u24/jre/lib/i386/server/libjvm.so[0x13f0ef7]
/usr/lib/jvm/sun-java-6u24/jre/lib/i386/server/libjvm.so[0x13d4aee]
/usr/lib/jvm/sun-java-6u24/jre/lib/i386/libjava.so(Java_java_lang_ref_Finalizer_invokeFinalizeMethod+0x6e)[0x11cb3e]
[0xb46de240]
[0xb46d218d]
[0xb46d218d]
[0xb46d218d]
[0xb46cf3e6]
/usr/lib/jvm/sun-java-6u24/jre/lib/i386/server/libjvm.so[0x13bdb21]
/usr/lib/jvm/sun-java-6u24/jre/lib/i386/server/libjvm.so[0x15b3478]
/usr/lib/jvm/sun-java-6u24/jre/lib/i386/server/libjvm.so[0x13bd395]
/usr/lib/jvm/sun-java-6u24/jre/lib/i386/server/libjvm.so[0x13bd458]
/usr/lib/jvm/sun-java-6u24/jre/lib/i386/server/libjvm.so[0x143fbe7]
/usr/lib/jvm/sun-java-6u24/jre/lib/i386/server/libjvm.so[0x16b404f]
/usr/lib/jvm/sun-java-6u24/jre/lib/i386/server/libjvm.so[0x15b4a6e]
/lib/libpthread.so.0[0x8fa842]
/lib/libc.so.6(clone+0x5e)[0xc6c4ce]
======= Memory map: ========
00110000-00133000 r-xp 00000000 08:01 106948
/usr/lib/jvm/sun-java-6u24/jre/lib/i386/libjava.so
00133000-00135000 rw-p 00023000 08:01 106948
/usr/lib/jvm/sun-java-6u24/jre/lib/i386/libjava.so
00135000-00148000 r-xp 00000000 08:01 74629 /lib/libnsl-2.5.so
00148000-00149000 r--p 00012000 08:01 74629 /lib/libnsl-2.5.so
00149000-0014a000 rw-p 00013000 08:01 74629 /lib/libnsl-2.5.so
0014a000-0014c000 rw-p 00000000 00:00 0
0014c000-0014f000 ---p 00000000 00:00 0
0014f000-0019d000 rwxp 00000000 00:00 0
0019d000-001d7000 r-xp 00000000 08:01 106944
/usr/lib/jvm/sun-java-6u24/jre/lib/i386/libjdwp.so
001d7000-001d8000 rw-p 00039000 08:01 106944
/usr/lib/jvm/sun-java-6u24/jre/lib/i386/libjdwp.so
001d8000-001d9000 ---p 00000000 00:00 0
001d9000-00259000 rwxp 00000000 00:00 0
00259000-0026d000 r-xp 00000000 08:01 106885
/usr/lib/jvm/sun-java-6u24/jre/lib/i386/libnet.so
0026d000-0026e000 rw-p 00013000 08:01 106885
/usr/lib/jvm/sun-java-6u24/jre/lib/i386/libnet.so
0026e000-00273000 r-xp 00000000 08:01 106769
/usr/lib/jvm/sun-java-6u24/jre/lib/i386/headless/libmawt.so
00273000-00274000 rw-p 00004000 08:01 106769
/usr/lib/jvm/sun-java-6u24/jre/lib/i386/headless/libmawt.so
00276000-00290000 r-xp 00000000 08:01 74651 /lib/ld-2.5.so
00290000-00291000 r--p 00019000 08:01 74651 /lib/ld-2.5.so
00291000-00292000 rw-p 0001a000 08:01 74651 /lib/ld-2.5.so
00292000-00295000 ---p 00000000 00:00 0
00295000-002e3000 rwxp 00000000 00:00 0
002e3000-002e8000 r-xp 00000000 08:01 212038
/usr/lib/libwsman_curl_client_transport.so.1.0.0
002e8000-002e9000 rw-p 00004000 08:01 212038
/usr/lib/libwsman_curl_client_transport.so.1.0.0
......................................
Sometimes I see "invalid pointer" as well. It seems a bug to the
libvirt java API. Has anyone seen this error before? Thanks.
Unfortunately, java bindings are not kept in such close sync as other
bindings (python for instance).
However, that backtrace is cagey. It doesn't ring any bell to me.
Michal