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

[Man Cao]

On Tue, 23 Aug 2022 20:05:46 GMT, Thomas Stuefe <stuefe at openjdk.org> wrote:

>> @caoman I'm interested in what your launcher does, or is, since I have almost never encountered signal chaining in the field. Would you mind sharing what product the launcher belongs to, and why you enable signal chaining?
>
>> @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.

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

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