Apache OpenOffice (AOO) Bugzilla – Issue 113687
Crash reporter not active on OOO330_m2
Last modified: 2017-05-20 09:16:05 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"
@obo: Please can you have a look? I was told, too, that the Crash Reporter is still active for milestones on the release codelines.
Not working in OOO330m3 and OOO330m4.
@kz: please can you look into this? thanks
I tested on ubuntu 10.04 and it is active with OOO330m2, only win version not contain this feature.
@mav: may be your changes in sal/osl/w32/signal.cxx (signal.c removed) ? changeset 266105 bd05bded0987
CCed: obo
CCed: cd
reassign, setting target + prio
mav->cd: Assigning to you as discussed.
cd: Started.
cd->mav: I found the root cause why the crash reporter doesn't work anymore.
cd: Set regression keyword because the root cause was introduced for the 3.3 release.
cd->of: Please verify.
of: Looks good for me in cws fwk156.
*** Issue 113211 has been marked as a duplicate of this issue. ***