Is there any other information I could collect to help troubleshoot this problem? How could I check if VM runs with attach disabled?
I noticed the same behavior when trying to connect to the process using JConsole: JConsole displays the sample app in the list and when I try to connect it finally displays an error that it cannot connect whereas the sample app prints thread dump on its console. On Thu, Nov 21, 2013 at 7:18 PM, Alan Bateman <alan.bate...@oracle.com>wrote: > On 21/11/2013 14:47, David Holmes wrote: > >> >> I can recreate this using the minimal VM, which doesn't support >> libattach. So it definitely seems like something is going wrong in the >> attach process, but I can't say what. Not sure what debugging hooks we have >> for the attach mechanism ?? >> > The first attach involves signaling the target VM to start up the attach > mechanism. So for the minimal VM or a VM running with attach disabled (or > as Staffan pointed out, running with a different tmp directory) then the > target VM gets a SIGQUIT and just prints the thread dump. It's hard to say > what Piotr is running into but I think this at least explains it for the > minimal VM. > > -Alan >
