Hi,
your information was in such a way helpful, as my initial
thought is not
the problem.
Try to get a corefile. E.g. start a bash shell, type
ulimit -c unlimited
and let your program run. After the crash, you should get a
[core
dumped] output and a file named core or similar with a
current timestamp
should be somewhere. Then start again the gdb and replace
the pid with
the filename of the core file and type where (info shared
output is not
needed anymore).
Sadly, gdb often has problems with complex multithreaded
programs but
the core file analysis should work.
Bye,
Joerg
Morten Omholt Alver wrote:
> Joerg,
>
> thank you for your answer! I'm afraid I'm not
proficient with gdb, but
> maybe I can provide more data with some help.
>
>> when you set the coredumpsize to unlimited in your
shell, you should get
>> a core dump. Attach with the gdb to it ( gdb
/path/to/java-executable
>> /path/to/core-file).
>
>
> I tried starting my application and then attaching gdb
with the
> command "gdb java <PID>", and got the
following output:
>
> (gdb) where
> #0 0xa7f30c01 in pthread_cond_wait GLIBC_2.3.2 () from
> /lib/tls/libpthread.so.0
> #1 0xa7f3122f in pthread_cond_waitGLIBC_2.0
() from
> /lib/tls/libpthread.so.0
> #2 0xa78dacee in os::Linux::safe_cond_wait ()
> from
/usr/lib/jvm/java-1.5.0-sun-1.5.0.08/jre/lib/i386/client/lib
jvm.so
> #3 0xa78c6e34 in Monitor::wait () from
>
/usr/lib/jvm/java-1.5.0-sun-1.5.0.08/jre/lib/i386/client/lib
jvm.so
> #4 0xa7948a0d in Threads::destroy_vm ()
> from
/usr/lib/jvm/java-1.5.0-sun-1.5.0.08/jre/lib/i386/client/lib
jvm.so
> #5 0xa77f496e in jni_DestroyJavaVM () from
>
/usr/lib/jvm/java-1.5.0-sun-1.5.0.08/jre/lib/i386/client/lib
jvm.so
> #6 0x0804960d in ?? ()
> #7 0xa79c8e80 in jni_NativeInterface ()
> from
/usr/lib/jvm/java-1.5.0-sun-1.5.0.08/jre/lib/i386/client/lib
jvm.so
> #8 0x0805e840 in ?? ()
> #9 0x0816f78a in ?? ()
> #10 0x0805e830 in ?? ()
> #11 0xafa2f854 in ?? ()
> #12 0x00000fff in ?? ()
> #13 0x08059008 in ?? ()
> #14 0x00000000 in ?? ()
>
> (gdb) info shared
> From To Syms Read Shared Object
Library
> 0xa7f2d310 0xa7f351d4 Yes
/lib/tls/libpthread.so.0
> 0xa7f24c10 0xa7f25964 Yes /lib/tls/libdl.so.2
> 0xa7e06cb0 0xa7efcbdf Yes /lib/tls/libc.so.6
> 0xa7f52790 0xa7f632bf Yes /lib/ld-linux.so.2
> 0xa767a440 0xa798d000 Yes
>
/usr/lib/jvm/java-1.5.0-sun-1.5.0.08/jre/lib/i386/client/lib
jvm.so
> 0xa762e360 0xa7649bc4 Yes /lib/tls/libm.so.6
> 0xa7f49250 0xa7f4ce10 Yes
>
/usr/lib/jvm/java-1.5.0-sun-1.5.0.08/jre/lib/i386/native_thr
eads/libhpi.so
> 0xa7603570 0xa7610644 Yes
/lib/tls/libnsl.so.1
> 0xa7f3f110 0xa7f44274 Yes
/lib/tls/libnss_compat.so.2
> 0xa75f7c40 0xa75fd7b4 Yes
/lib/tls/libnss_nis.so.2
> 0xa75ecb80 0xa75f3514 Yes
/lib/tls/libnss_files.so.2
> 0xa76190d0 0xa761fc90 Yes
>
/usr/lib/jvm/java-1.5.0-sun-1.5.0.08/jre/lib/i386/libverify.
so
> 0xa75d1190 0xa75e58e0 Yes
>
/usr/lib/jvm/java-1.5.0-sun-1.5.0.08/jre/lib/i386/libjava.so
> 0xa75b8ca0 0xa75c38c0 Yes
>
/usr/lib/jvm/java-1.5.0-sun-1.5.0.08/jre/lib/i386/libzip.so
> 0xa1843d40 0xa188d8c0 Yes
>
/usr/lib/jvm/java-1.5.0-sun-1.5.0.08/jre/lib/i386/libawt.so
> 0xa1769b00 0xa1822c10 Yes
>
/usr/lib/jvm/java-1.5.0-sun-1.5.0.08/jre/lib/i386/libmlib_im
age.so
> 0xa1741960 0xa1762da0 Yes
>
/usr/lib/jvm/java-1.5.0-sun-1.5.0.08/jre/lib/i386/xawt/libma
wt.so
> 0xa1716660 0xa1720174 Yes
/usr/lib/libXext.so.6
> 0xa165f240 0xa16ccd44 Yes
/usr/lib/libX11.so.6
> 0xa164ba00 0xa164c604 Yes
/usr/lib/libXau.so.6
> 0xa1646f00 0xa1648ae4 Yes
/usr/lib/libXdmcp.so.6
> 0xa15d6d10 0xa162e980 Yes
>
/usr/lib/jvm/java-1.5.0-sun-1.5.0.08/jre/lib/i386/libfontman
ager.so
> 0xa17346b0 0xa1735564 Yes
/usr/lib/X11/locale/common/xlcDef.so.2
> 0xa172d2a0 0xa1732404 Yes
/usr/lib/libXcursor.so.1
> 0xa17243e0 0xa1729a54 Yes
/usr/lib/libXrender.so.1
> 0xa1537f30 0xa153a1b4 Yes
/usr/lib/libXfixes.so.3
> 0xa1542060 0xa154eb10 Yes
>
/usr/lib/jvm/java-1.5.0-sun-1.5.0.08/jre/lib/i386/libnet.so
> 0xa11897a0 0xa118c650 Yes
>
/usr/lib/jvm/java-1.5.0-sun-1.5.0.08/jre/lib/i386/libnio.so
> 0xa116f190 0xa1183d14 Yes
/usr/lib/X11/locale/common/ximcp.so.2
> 0xa1162480 0xa1162e54 Yes
/usr/lib/gconv/ISO8859-1.so
> 0xa153c9a0 0xa153d1c4 Yes
/usr/lib/openoffice/program/libjpipe.so
> 0xa0de0d20 0xa0e090c4 Yes
> /usr/lib/openoffice/program/libuno_sal.so.3
> 0xa0d2a800 0xa0da60f4 Yes
/usr/lib/libstdc++.so.6
> 0xa11438a0 0xa114abf4 Yes /lib/libgcc_s.so.1
> 0xa113b3e0 0xa113f714 Yes /lib/libpam.so.0
> 0xa110c840 0xa110fa84 Yes
/lib/tls/libcrypt.so.1
>
>
> This is after I connect to OpenOffice, but before I
shut the
> application down (and crash). Can I do something to get
information
> after the crash? I just tried using the
"continue" command in gdb, and
> my application shuts down with:
>
> (gdb) continue
> Continuing.
> [New Thread -1588892752 (LWP 5267)]
> Cannot get thread event message: debugger service
failed
>
>
>> Did the java and OpenOffice come with your
distribution ? Both (OOo and
>> java) should have been compiled with the same gcc
version, otherwise
>> exception handling might fail (Probably the native
implementation tries
>> to throw a native c++ exception which leads to the
crash).
>
>
> I am running on Debian unstable, and Java 1.5 and
OpenOffice are both
> installed normally by the package manager. Both are the
latest
> version, though I'm not sure if this implies that they
are built with
> the same gcc version.
>
>
> Regards,
> Morten
>
>
------------------------------------------------------------
---------
> To unsubscribe, e-mail: dev-unsubscribeudk.openoffice.org
> For additional commands, e-mail: dev-helpudk.openoffice.org
>
>
------------------------------------------------------------
---------
To unsubscribe, e-mail: dev-unsubscribeudk.openoffice.org
For additional commands, e-mail: dev-helpudk.openoffice.org
|