jstack can't attach to JVM (OS X)

[Staffan Larsen]

Thanks for the excellent bugreport!

I've had a quick look today but haven't yet figured out what the problem is. What happens is that somehow the process becomes immune to the SIGQUIT that jstack sends to it when it wants to attach. Instead of running jstack, one can also do "kill -QUIT <pid>" and with this code no thread stacks are printed (as they normally will be).

I'll continue looking,
/Staffan 

On 23 aug 2013, at 07:20, Martin Traverso <mtraverso at gmail.com> wrote:

> I have a program that causes jstack and jcmd to fail to attach to the JVM on OS X. Unfortunately, it uses a third-party library, so I'm not sure what's the magic incantation that causes this to happen. 
> 
> I wrote a small test case using this library that reproduces the problem. You can find the code here: https://github.com/martint/jstackissue.
> 
> I've seen the problem on both 1.7.0_25-b15 and 1.8.0-ea-b100 on OS X, but not on Java 6. It doesn't seem to happen on Linux, either.
> 
> One interesting data point is that if I run jstack before the code makes the call to the library, it works, and continues to work even after that call is complete. On the other hand, if run jstack for the first time *after* the call to the library, it won't work at all.
> 
> Any ideas?
> 
> Thanks!
> Martin

-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://mail.openjdk.java.net/pipermail/serviceability-dev/attachments/20130823/9459a7dd/attachment.html