RFR: 8292695: SIGQUIT and jcmd attaching mechanism does not work with signal chaining library [v3]

Thomas Stuefe stuefe at openjdk.org
Fri Sep 9 05:35:44 UTC 2022


On Thu, 8 Sep 2022 18:17:29 GMT, Man Cao <manc at openjdk.org> wrote:

>> test/hotspot/jtreg/runtime/Thread/TestBreakSignalThreadDump.java line 38:
>> 
>>> 36:  * @bug 8292695
>>> 37:  * @summary Check that Ctrl-\ causes HotSpot VM to print a full thread dump when signal chaining is used.
>>> 38:  * @requires os.family == "linux" | os.family == "mac"
>> 
>> Why not just !Windows? Aix, the BSDs, Solaris if this is downported should work too.
>
> https://docs.oracle.com/en/java/javase/17/troubleshoot/handle-signals-and-exceptions.html#GUID-CB49A2A7-2A9F-4C18-948F-6D4A96FF688D says signal chaining is available only on Linux and macOS. Should the doc be updated?
> 
> Also, the tests in `test/hotspot/jtreg/runtime/signal/` have "!windows && !aix". I'm not sure why they exclude aix, should this test exclude aix similarly?

Well, Solaris support was removed from JDK in 16, but older releases still support it, see: https://docs.oracle.com/en/java/javase/11/troubleshoot/handle-signals-and-exceptions.html#GUID-F012840D-8E5A-4B6D-8E49-0129A9EE46DB.

As  for AIX, the reason given for the exclusions in other tests is that we cannot run in the primordial thread on AIX. That is true but I'm not sure what this has to do with the signal tests, and I believe libjsig and the other stuff should just work on AIX. I have to dig in our older sources (this stems from the pre-OpenJDK times at SAP).

For now, I'd use !windows && !aix. AIX we can take care of later, but Solaris I would like to support here. Because of backporting, mainly.

-------------

PR: https://git.openjdk.org/jdk/pull/9955


More information about the hotspot-runtime-dev mailing list