This is the mail archive of the java@gcc.gnu.org mailing list for the Java project.

Index Nav:	[Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav:	[Date Prev] [Date Next]	[Thread Prev] [Thread Next]
Other format:	[Raw text]

Re: GCJ Thread Dump

From: Bryce McKinlay <mckinlay at redhat dot com>
To: Andrew Haley <aph at redhat dot com>
Cc: Mark Anderson <mark at panonet dot net>, java at gcc dot gnu dot org
Date: Wed, 09 Feb 2005 17:02:02 -0500
Subject: Re: GCJ Thread Dump
References: <200502091034.37317.mark@panonet.net> <16905.61846.186408.440564@cuddles.cambridge.redhat.com>

Andrew Haley wrote:

Mark Anderson writes: > Is there any way to get a thread dump from a running GCJ application in the > same way you can send a kill -3 signal to the Sun JVM?
No, there isn't, and it would be extremely hard to do.  Whan we have a
problem like this, we attach gdb to the process.

I'm curious - why is this so difficult? I think Sun's implementation shows what locks are held by each thread, along with the stack trace, which might be tricky. However, I don't see why plain old thread dumps would be so hard given that we can already unwind through signal handlers. Note that there is a enhancement request for this:

http://gcc.gnu.org/bugzilla/show_bug.cgi?id=15686

Regards

Bryce

Follow-Ups:
- Re: GCJ Thread Dump
  - From: David Daney

References:
- GCJ Thread Dump
  - From: Mark Anderson
- Re: GCJ Thread Dump
  - From: Andrew Haley

Index Nav:	[Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav:	[Date Prev] [Date Next]	[Thread Prev] [Thread Next]