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

[Thomas Stuefe]

On Tue, 6 Sep 2022 23:07:39 GMT, Man Cao <manc at openjdk.org> wrote:

>>> @tstuefe Our launcher is equipped with almost all our Java applications. It basically does what bin/java does, but with several additional features. One main motivation to have our own launcher, is to static link all user-defined JNI dependency libraries with the launcher, so the applications do not need to use `System.loadLibrary()` to load `.so` files dynamically. Using static linking instead of dynamically loading `.so` files is core characteristic of our deployment environment for almost all languages (C, C++, Java, Python, Go). @jianglizhou is actually working on a project that also statically links HotSpot (`libjvm.so` and other `.so` files) with the our launcher as well.
>> 
>> That is interesting. Do you link statically to improve startup speed, or for some other reason?
>
> @tstuefe Any feedback? I'd like to get this submitted soon to unblock our internal use cases relying on SIGQUIT and jcmd.

@caoman While looking at this, I think I found an unrelated bug in libjsig. https://bugs.openjdk.org/browse/JDK-8293466 Could you eyeball it and tell me if my assumption is correct?

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

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