JDK-4408646 : JVM_handle_solaris_signal must be a global function
  • Type: Bug
  • Component: hotspot
  • Sub-Component: runtime
  • Affected Version: 1.3.0
  • Priority: P1
  • Status: Closed
  • Resolution: Fixed
  • OS: solaris_7
  • CPU: generic
  • Submitted: 2001-01-26
  • Updated: 2022-04-05
  • Resolved: 2001-05-04
The Version table provides details related to the release that this issue/RFE will be addressed.

Unresolved : Release in which this issue/RFE will be addressed.
Resolved: Release in which this issue/RFE has been resolved.
Fixed : Release in which this issue/RFE has been fixed. The release containing this fix may be available for download as an Early Access Release or a General Availability Release.

To download the current JDK release, click here.
Other
1.3.0_03 03Fixed
Related Reports
Relates :  
Relates :  
Description
This is a bug with the JDK1.3.0 signal handling mechanism:

Bug 4361067 documents how third-party software can co-exist with the JVM's own
signal handler through the use of JVM_handle_linux_signal.
Unfortunately, the JVM_handle_solaris_signal function is only a local function,
not a global, so third-party software that needs to handle signals cannot
invoke the JVM's signal handlers, so there is no consistency between the
Linux and Solaris platforms.

I am raising this bug on behalf of an ISV who needs to capture some of the
signals that are also of interest to the JVM:

The servers in CB need to keep track of the signals SEGV, SIGILL, SIGFPE
and SIGABRT.  If these signals are received we need to record the
information related to the stack when this signal is raised and restart the
server.  This is done using the signal handlers.  So it is very important
for us handle these signals.  If we have access to the call
JVM_handle_solaris_signal then we can call it and can proceed with our
processing once the JVM is through with its processing.

Comments
CONVERTED DATA BugTraq+ Release Management Values COMMIT TO FIX: 1.3.0_03 FIXED IN: 1.3.0_03 INTEGRATED IN: 1.3.0_03 VERIFIED IN: 1.3.0_03
14-06-2004

EVALUATION export the JVM_handle_solaris_signal in the mapfile-vers file
11-06-2004

WORK AROUND Turn off JVM signal handling with -XX:+AllowUserSignalHandlers The big disadvantage is that JVM_handle_solaris_signal cannot be called, so the JVM can never handle such signals. This may not be such a big deal, because the ISV restarts their server and (presumably) loads a new copy of the JVM, but I don't know the full implications of this.
11-06-2004

PUBLIC COMMENTS Make JVM_handle_solaris_signal a global function so that third-party signal handlers can co-exist with the JVM's own signal handler, for consistency with the Linux platform (see bug 4361067)
10-06-2004

SUGGESTED FIX Make JVM_handle_solaris_signal a global function so that third-party code can call it. *** mapfile-vers.org Wed Feb 14 13:08:35 2001 --- mapfile-vers Wed Feb 14 13:13:51 2001 *************** *** 183,188 **** --- 183,189 ---- JVM_UnloadLibrary; JVM_Write; JVM_Yield; + JVM_handle_solaris_signal; # miscellaneous functions jio_fprintf; murali.earagolla@Eng 2001-02-28
28-02-2001