Staffan, Thank you for the explanation.
The fix looks good for me. -Dmitry On 2016-10-21 10:49, Staffan Larsen wrote: > Dmitry, > > I would like to avoid running SA-based tools in the timeout handler since on > macOS they pop up dialogs asking for permission to attach to the process. > This is problematic in our testing infrastructure. Instead, I hope we can run > jhsdb on the core file that is generated. > > I tried doing this automatically in the timeout handler, but could not find a > simple way to do it. jhsdb requires the path to the executable and the > timeout handler does not know this. Perhaps a future enhancement to the > timeout handler could fix this. > > /Staffan > >> On 20 Oct 2016, at 22:12, Dmitry Samersoff <dmitry.samers...@oracle.com> >> wrote: >> >> Staffan, >> >> Could you add >> jhsdb jstack --mixed --pid <pid> >> to get mixed stack trace when it possible? >> >> -Dmitry >> >> On 2016-10-20 14:42, Staffan Larsen wrote: >>> Please review this small update to the list of tools that the jtreg >>> timeouthandler runs when a timeout is hit. This change removes all calls to >>> the old SA-tools and instead uses Diagnostic Commands to gather the same >>> information. The possible drawback is that Diagnostic Commands do not work >>> on processes where the JVM is completely hung, but in that case we can >>> fallback to running the SA-tools on the core file that is also generated. >>> >>> webrev: http://cr.openjdk.java.net/~sla/8168409/webrev.00 >>> <http://cr.openjdk.java.net/~sla/8168409/webrev.00> >>> bug: https://bugs.openjdk.java.net/browse/JDK-8168409 >>> <https://bugs.openjdk.java.net/browse/JDK-8168409> >>> >>> Thanks, >>> /Staffan >>> >> >> >> -- >> Dmitry Samersoff >> Oracle Java development team, Saint Petersburg, Russia >> * I would love to change the world, but they won't give me the sources. > -- Dmitry Samersoff Oracle Java development team, Saint Petersburg, Russia * I would love to change the world, but they won't give me the sources.
