Re: Output from sudo kill -QUIT pid

Use gdb.
gdb <executable> in that case the JVM
then issue an attach to the process
Then use the gdb "signal" to send the signal
or better type control-C to interrupt back to gdb.
Then you can ask for a stack trace ("bt" command) and also examine 
(backtrace) different threads.

Fabien
On Nov 19, 2004, at 11:29 AM, Brendan Duddridge wrote:

> Hi,
>
> Does anyone know where the output of doing 'sudo kill -QUIT pid' goes? 
> I
> have an application that is not responding anymore and I'd like to see 
> the
> stack trace of where it's waiting. The app was started up with 
> Monitor. I
> know that if I start it from the command line and do a control-\, then 
> I
> will see the stack trace. I want an equivalent way of getting that
> information from a Monitor started application.
>
> WO 5.2.3, OS X Server 10.3.5.
>
> Thanks,