To comment on the following update, log in, then open the issue: http://www.openoffice.org/issues/show_bug.cgi?id=108411 Issue #|108411 Summary|let SID_CRASH really crash Component|framework Version|DEV300m68 Platform|All URL| OS/Version|All Status|NEW Status whiteboard| Keywords| Resolution| Issue type|DEFECT Priority|P3 Subcomponent|code Assigned to|sb Reported by|sb
------- Additional comments from [email protected] Mon Jan 18 12:04:10 +0000 2010 ------- The code to handle SID_CRASH (.uno:Crash, slot:6645) in sfx2/source/appl/appserv.cxx calls GetpApp->Exception(EXC_SYSTEM) instead of causing a real crash, which would go through the sal signal handler. A real crash would be more helpful when using SID_CRASH to analyze the crash-handling behavior of OOo. (For example, adding <menu:menuitem menu:id=".uno:Crash"/> to framework/uiconfig/startmodule/menubar/menubar.xml and/or sw/uiconfig/swriter/menubar/menubar.xml to have an (unlabeled) menu entry in Start Center resp. Writer that lets OOo crash. Using a Basic macro, say, instead has the disadvantage that many "Tools - Macros" items initialize all scripting frameworks and thus start a JVM, where an in-process JVM can have a strong impact on OOo's crash-handling behavior.) --------------------------------------------------------------------- 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]
