«

halfdog wrote:

> PS: Bad? luck Windows users, seems that this ultra-chaotic, scratch
> your nose with your feets-geek tool is only available for linux

Thanks for the follow up. It does sound rather a rather, um, baroque way of
getting at the data you need. But if it works, it works....

-- chris

With the help of a guy from javasoft I managed to do it all: Debug a
dump of a java vm:

$ cat << END > gdb.commands
> gcore tomcat.core
> detach
> quit
> END
$ gdb --pid 26003 -x gdb.commands
$ jsadebugd ..../jdk1.5.0_06/bin/java tomcat.core DebugServer &
$ jdb -connect
sun.jvm.hotspot.jdi.SADebugServerAttachingConnecto r:debugServerName=DebugServer@localhost

You can inspect all the data (threads, stack frames, local variables,
objects) just as if you would have attached to a live VM, only
modifications do not work (step, continue, set...) because a VM core
dump is dead.

This is a really strange way to debug a java application, I never
thought that it could work that way.

Here is a shell script to take and save thread dump in a text file. I have written a shell script to take the thread dump automatically.

visit : http://www.technotechi.com/2012/12/s...read-dump.html

It might help you.