Issue 113687

Summary: Crash reporter not active on OOO330_m2
Product: QA Reporter: r4zoli <r4zoli>
Component: tcmAssignee: Olaf Felka <olaf-openoffice>
Status: CLOSED FIXED QA Contact: issues@qa <issues>
Severity: Trivial    
Priority: P2 CC: carsten.driesner, issues, jens-heiner.rechtien, kurt.zenker, marcus, mikhail.voytenko, oliver.bolte
Version: OOO330m1Keywords: regression
Target Milestone: ---   
Hardware: All   
OS: Windows 7   
Issue Type: DEFECT Latest Confirmation in: ---
Developer Difficulty: ---
Issue Depends on:    
Issue Blocks: 111112    

Description r4zoli 2010-08-05 16:05:56 UTC
Crash reporter not active on OOO330_m2.

Excerpt from one of the qa-dev list mail:
"DEV300m83 is a developer snapshot. Since quite some time now those are not
compiled with debugger information anymore and do not have crash reporting
enabled anymore. 
"No crash reporting coming up" is the normal behaviour for developer snapshots
nowadays.

one addition:
This is new for DEV300 milestones. But for release codeline milestones (OOO320,
OOO330) the crash reporting will still work.

Best regards

Marcus"
Comment 1 Marcus 2010-08-06 08:36:23 UTC
@obo: Please can you have a look? I was told, too, that the Crash Reporter is
still active for milestones on the release codelines.
Comment 2 r4zoli 2010-08-13 09:34:32 UTC
Not working in OOO330m3 and OOO330m4.
Comment 3 Marcus 2010-08-13 09:37:50 UTC
@kz: please can you look into this? thanks
Comment 4 r4zoli 2010-08-13 09:46:55 UTC
I tested on ubuntu 10.04 and it is active with OOO330m2, only win version not
contain this feature.
Comment 5 oliver.bolte 2010-08-23 14:14:03 UTC
@mav: may be your changes in sal/osl/w32/signal.cxx (signal.c removed) ?
changeset 266105	bd05bded0987
Comment 6 oliver.bolte 2010-08-23 14:15:37 UTC
CCed: obo
Comment 7 oliver.bolte 2010-08-24 09:30:35 UTC
CCed: cd
Comment 8 oliver.bolte 2010-08-24 09:43:26 UTC
reassign, setting target + prio
Comment 9 mikhail.voytenko 2010-08-31 11:05:21 UTC
mav->cd: Assigning to you as discussed.
Comment 10 carsten.driesner 2010-09-02 11:44:25 UTC
cd: Started.
Comment 11 carsten.driesner 2010-09-02 18:36:39 UTC
cd->mav: I found the root cause why the crash reporter doesn't work anymore.
Comment 12 carsten.driesner 2010-09-06 10:02:19 UTC
cd: Set regression keyword because the root cause was introduced for the 3.3
release.
Comment 13 carsten.driesner 2010-09-07 11:50:50 UTC
cd->of: Please verify.
Comment 14 Olaf Felka 2010-09-10 13:23:52 UTC
of: Looks good for me in cws fwk156.
Comment 15 Stephan Bergmann 2010-09-17 14:23:40 UTC
*** Issue 113211 has been marked as a duplicate of this issue. ***