To comment on the following update, log in, then open the issue: http://www.openoffice.org/issues/show_bug.cgi?id=108476 Issue #|108476 Summary|in-process JVM deactivates osl signal handler Component|udk Version|DEV300m69 Platform|All URL| OS/Version|All Status|NEW Status whiteboard| Keywords| Resolution| Issue type|PATCH Priority|P3 Subcomponent|code Assigned to|sb Reported by|sb
------- Additional comments from [email protected] Wed Jan 20 09:56:07 +0000 2010 ------- jfw_plugin_startJavaVirtualMachine in jvmfwk/plugins/sunmajor/pluginlib/sunjavaplugin.cxx contains an #ifdef UNX block of code to reset some signals (SIGSEGV, SIGPIPE, SIGBUS, etc.) to SIG_DFL before calling JNI_CreateJavaVM, commented as: "The office sets a signal handler at startup. That causes a crash with java 1.3 under Solaris. To make it work, we set back the handler." On Solaris (unxsoli4.pro, unxsols4.pro) at least with somewhat recent JVMs (1.5.0_16, 1.6.0_15, 1.6.0_16), this causes OOo to terminate (with the JVM outputting crash information to stderr and a hs_err_pid* file in cwd) upon typical crashes (incurring SIGSEGV or SIGBUS), instead of the OOo crash handling mechanism stepping in. On Linux (unxlngi6.pro), the OOo crash handling mechanism is started "by accident" (the original SIGSEGV is not passed from the JVM signal handler to the osl one, as it has been reset by the above code block; however, the JVM shutdown sequence leads to an abort call, the resulting SIGABRT being delivered to the sal signal handler, as it has not been reset by the above code block), but the JVM nonetheless outputs its crash information to stderr and a hs_err_pid* file in cwd. --------------------------------------------------------------------- Please do not reply to this automatically generated notification from Issue Tracker. Please log onto the website and enter your comments. http://qa.openoffice.org/issue_handling/project_issues.html#notification --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected] --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
