Issue 108411 - let SID_CRASH really crash
Summary: let SID_CRASH really crash
Alias: None
Product: General
Classification: Code
Component: code (show other issues)
Version: DEV300m68
Hardware: All All
: P3 Trivial (vote)
Target Milestone: OOo 3.3
Assignee: thorsten.martens
QA Contact: issues@framework
Depends on:
Reported: 2010-01-18 12:04 UTC by Stephan Bergmann
Modified: 2017-05-20 10:23 UTC (History)
1 user (show)

See Also:
Issue Type: DEFECT
Latest Confirmation in: ---
Developer Difficulty: ---


Note You need to log in before you can comment on or make changes to this issue.
Description Stephan Bergmann 2010-01-18 12:04:10 UTC
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.)
Comment 1 Stephan Bergmann 2010-01-18 12:06:35 UTC
fixed as <>
Comment 2 Stephan Bergmann 2010-02-08 10:06:59 UTC
@tm: please verify
Comment 3 joerg.skottke 2010-02-23 08:31:09 UTC
Added slot "crash" to e_all.sid

The slot can be used to provide an automated test for the crash reporter which is not done in 
cws sb119 (need timeslot for this)