libjsig deprecation warning, lenience for signal(SIGPIPE, SIG_IGN)?

Mikael Sterner msterner at openjdk.mxy.se
Fri Apr 11 04:59:44 UTC 2025


Hi,

During migration of a desktop software from Java 11 to
Java 21 we started seeing the libjsig deprecation warnings.
That's fine and appreciated as a heads-up, and I also notice
that some nice changes to the message logic have been done 
for Java 25.

However, tracing what triggered our warnings, I wonder if you
think it could make sense to be lenient about calls to deprecated
signal() method that just want to ignore a signal with SIG_IGN,
in particular SIGPIPE? This pattern seems to be used in several
Gnome libraries:

 - https://gitlab.gnome.org/GNOME/gtk/-/blob/main/gtk/gtkmain.c?ref_type=heads#L555
 - https://gitlab.gnome.org/GNOME/glib/-/blob/main/gio/gsocket.c?ref_type=heads#L967
 - https://gitlab.gnome.org/GNOME/gvfs/-/blob/master/client/gdaemonvfs.c#L304

Or would it be better to report such calls as deficiencies in
these libraries, with the libjsig warnings as evidence?

Yours,
Mikael Sterner


More information about the hotspot-runtime-dev mailing list