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:

> > @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?

It is not about startup speed, but mainly to ensure correct version and simplify deployment. It is very similar to the advantages of static library as stated on Wikipedia: https://en.wikipedia.org/wiki/Static_library.
@jianglizhou will share more details about this project in a separate email thread or in a public talk soon, so stay tuned.

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

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