Issue 63819 - crash reporter doesn't start when getting signal
Summary: crash reporter doesn't start when getting signal
Status: CLOSED FIXED
Alias: None
Product: General
Classification: Code
Component: code (show other issues)
Version: current
Hardware: All Windows XP
: P2 Trivial (vote)
Target Milestone: OOo 2.0.3
Assignee: Joost Andrae
QA Contact: issues@framework
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2006-03-30 15:27 UTC by Joost Andrae
Modified: 2006-05-05 11:20 UTC (History)
1 user (show)

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

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this issue.
Description Joost Andrae 2006-03-30 15:27:40 UTC 
JA->HRO: as shown the crash reporter doesn't start in src680m162 wntmsci10.pro
if called by a kill -NULL from your kill.exe

cookbook:
soffice.exe -writer
open soffice native filepicker
kill -NULL soffice.bin

--> now the crash reporter should show up but it doesn't.

This issue currently prevents the release of src680m162 as OOoDev2.0 Developer
Snapshot build. That's the reason why it is P1. Last tested in src680m160
Comment 1 Joost Andrae 2006-03-30 15:28:36 UTC 
JA: reassigned to hro
Comment 2 Joost Andrae 2006-03-30 16:56:03 UTC 
windows only. unxlngi6.pro, unxsoli4.pro and unxsols4.pro not affected
Comment 3 Joost Andrae 2006-03-31 08:51:42 UTC 
JA: priorize the issue back to P2. It depends on having a dialog open within
OpenOffice.org if the crash reporter can start or not. If I have no dialog open
then it can start. This issue is still definded as showstopper for the 2.0.3
release but I can live with this bug within the src680m162 OOoDev build.
Comment 4 hennes.rohling 2006-03-31 10:00:03 UTC 
hro@as: 

Broken with fwk34

vcl/source/salinst.cxx, Line 1126

Replace the line:

return EXCEPTION_EXECUTE_HANDLER;

with

return UnhandledExceptionFilter( nExcept, pExceptionInfo );
Comment 5 andreas.schluens 2006-04-07 09:08:49 UTC 
AS->HRO: I've changed the code as you mentioned ... but I'm not sure that it solves 
ALL problems here. Because real C++ (most likly UNO) exceptions are rethrown 
anyway. Because they should reach our Desktop::Main() method. But  nobody can 
guarantee that user32.dll does not redirect such exceptions to /dev/null also .-)
We will see ...
Comment 6 Joost Andrae 2006-04-07 16:35:30 UTC 
JA->AS: please send this issue back to UL when it's Ready4QA as I'm on vacation
next week. I've already talked to him regarding the test scenario.
Comment 7 andreas.schluens 2006-04-12 13:51:09 UTC 
AS->UL: Please verify this task on cws [fwk37]. THX.

re-open issue and reassign to ul@openoffice.org
Comment 8 andreas.schluens 2006-04-12 13:51:15 UTC 
reassign to ul@openoffice.org
Comment 9 andreas.schluens 2006-04-12 13:51:20 UTC 
reset resolution to FIXED
Comment 10 thorsten.martens 2006-04-18 12:17:41 UTC 
reassigned to ja.

re-open issue and reassign to ja
Comment 11 thorsten.martens 2006-04-18 12:17:45 UTC 
reassign to ja
Comment 12 thorsten.martens 2006-04-18 12:17:49 UTC 
reset resolution to FIXED
Comment 13 Joost Andrae 2006-04-18 13:00:58 UTC 
verified in cws fwk37
Comment 14 Joost Andrae 2006-05-05 11:20:13 UTC 
closing issue