Closed
Bug 444103
Opened 16 years ago
Closed 16 years ago
add ability to add string-formatted notes to crash report
Categories
(Toolkit :: Crash Reporting, defect)
Tracking
()
RESOLVED
FIXED
People
(Reporter: jaas, Assigned: ted)
References
Details
(Keywords: verified1.9.0.5)
Attachments
(2 files)
11.95 KB,
patch
|
benjamin
:
review+
dveditz
:
approval1.9.0.4-
|
Details | Diff | Splinter Review |
33.73 KB,
patch
|
dveditz
:
approval1.9.0.5+
|
Details | Diff | Splinter Review |
We should add the ability to add string-formatted notes to crash report. This could be used, for example, to store the information contained in an exception object info field to help us fix crashes that come from exceptions.
This would be a sort of catch-all field of textual data that the server stores and displays via socorro. This would probably involve adding a method to the nsICrashReporter interface that is like the existing annotateReport.
Assignee | ||
Comment 1•16 years ago
|
||
This adds a new method to nsICrashReporter, appendAppNotesToCrashReport(in ACString data). It appends whatever you pass it to a single string, and adds it to the crash report in a field named "Notes".
I also reworked the unit tests a little bit while adding a test for this method.
Attachment #331176 -
Flags: review?(benjamin)
Comment 2•16 years ago
|
||
Comment on attachment 331176 [details] [diff] [review]
add appendAppNotesToCrashReport method to nsICrashReporter interface+impl
You need to rev the IID of nsICrashReporter before final push.
Attachment #331176 -
Flags: review?(benjamin) → review+
Assignee | ||
Comment 3•16 years ago
|
||
rev'ed the IID and pushed to mozilla-central:
http://hg.mozilla.org/mozilla-central/index.cgi/rev/61c0a4ca72e4
Status: NEW → RESOLVED
Closed: 16 years ago
Resolution: --- → FIXED
Comment on attachment 331176 [details] [diff] [review]
add appendAppNotesToCrashReport method to nsICrashReporter interface+impl
Requesting approval for 1.9.0.x for this patch, since it (in conjunction with bug 451709) would really help decipher the extremely high number of Mac crashes that are lumped under nsObjCExceptionLogAbort(NSException*).
Attachment #331176 -
Flags: approval1.9.0.4?
Comment 5•16 years ago
|
||
Comment on attachment 331176 [details] [diff] [review]
add appendAppNotesToCrashReport method to nsICrashReporter interface+impl
Better to get this early next time than late this time.
Attachment #331176 -
Flags: approval1.9.0.5?
Attachment #331176 -
Flags: approval1.9.0.4?
Attachment #331176 -
Flags: approval1.9.0.4-
Comment 6•16 years ago
|
||
Ted, can you provide a new patch for this that doesn't change the existing interface?
Comment 7•16 years ago
|
||
Ted, any update here?
Assignee | ||
Comment 8•16 years ago
|
||
Sorry, I've been really busy on other things. I can do a branch patch, I just need to find some time.
Updated•16 years ago
|
Whiteboard: [needs 1.9.0 patch]
Assignee | ||
Updated•16 years ago
|
Attachment #331176 -
Flags: approval1.9.0.5?
Assignee | ||
Comment 9•16 years ago
|
||
Ok, this is a branch patch including the patch here as well as the patch from bug 451709. Added a new interface with the added methods and changed the iface references in the code. Works fine, I have an updated CrashMe extension that can be used to test, I'll post directions shortly.
Attachment #348212 -
Flags: approval1.9.0.5?
Assignee | ||
Updated•16 years ago
|
Whiteboard: [needs 1.9.0 patch]
Updated•16 years ago
|
Attachment #348212 -
Flags: approval1.9.0.5? → approval1.9.0.5+
Comment 10•16 years ago
|
||
Comment on attachment 348212 [details] [diff] [review]
rollup branch patch for this bug + bug 451709
often it makes more sense to inherit from the original interface rather than a parallel unrelated _BRANCH interface.
Approved for 1.9.0.5, a=dveditz for release-drivers
Comment 11•16 years ago
|
||
please add the "fixed1.9.0.5" to bug 451709 as well when you check this in so QA remembers to verify that part of the fix.
Assignee | ||
Comment 12•16 years ago
|
||
Will do. Going to try to add a litmus test to that bug as well.
Checking in toolkit/crashreporter/mac_utils.h;
/cvsroot/mozilla/toolkit/crashreporter/mac_utils.h,v <-- mac_utils.h
new revision: 1.2; previous revision: 1.1
done
Checking in toolkit/crashreporter/mac_utils.mm;
/cvsroot/mozilla/toolkit/crashreporter/mac_utils.mm,v <-- mac_utils.mm
new revision: 1.3; previous revision: 1.2
done
Checking in toolkit/crashreporter/nsExceptionHandler.cpp;
/cvsroot/mozilla/toolkit/crashreporter/nsExceptionHandler.cpp,v <-- nsExceptionHandler.cpp
new revision: 1.39; previous revision: 1.38
done
Checking in toolkit/crashreporter/nsExceptionHandler.h;
/cvsroot/mozilla/toolkit/crashreporter/nsExceptionHandler.h,v <-- nsExceptionHandler.h
new revision: 1.9; previous revision: 1.8
done
Checking in toolkit/crashreporter/test/TestCrashReporterAPI.cpp;
/cvsroot/mozilla/toolkit/crashreporter/test/TestCrashReporterAPI.cpp,v <-- TestCrashReporterAPI.cpp
new revision: 1.7; previous revision: 1.6
done
Checking in toolkit/xre/MacLaunchHelper.h;
/cvsroot/mozilla/toolkit/xre/MacLaunchHelper.h,v <-- MacLaunchHelper.h
new revision: 1.6; previous revision: 1.5
done
Removing toolkit/xre/MacLaunchHelper.m;
/cvsroot/mozilla/toolkit/xre/MacLaunchHelper.m,v <-- MacLaunchHelper.m
new revision: delete; previous revision: 1.9
done
RCS file: /cvsroot/mozilla/toolkit/xre/MacLaunchHelper.mm,v
done
Checking in toolkit/xre/MacLaunchHelper.mm;
/cvsroot/mozilla/toolkit/xre/MacLaunchHelper.mm,v <-- MacLaunchHelper.mm
initial revision: 1.1
done
Checking in toolkit/xre/Makefile.in;
/cvsroot/mozilla/toolkit/xre/Makefile.in,v <-- Makefile.in
new revision: 1.93; previous revision: 1.92
done
Checking in toolkit/xre/nsAppRunner.cpp;
/cvsroot/mozilla/toolkit/xre/nsAppRunner.cpp,v <-- nsAppRunner.cpp
new revision: 1.214; previous revision: 1.213
done
Checking in xpcom/base/nsObjCExceptions.h;
/cvsroot/mozilla/xpcom/base/nsObjCExceptions.h,v <-- nsObjCExceptions.h
new revision: 1.7; previous revision: 1.6
done
Checking in xpcom/system/nsICrashReporter.idl;
/cvsroot/mozilla/xpcom/system/nsICrashReporter.idl,v <-- nsICrashReporter.idl
new revision: 1.2; previous revision: 1.1
done
Keywords: fixed1.9.0.5
Assignee | ||
Comment 13•16 years ago
|
||
This fix can be verified along with bug 451709 in the steps in bug 451709 comment 18.
Comment 14•16 years ago
|
||
I believe this caused Bug 465233
Comment 15•16 years ago
|
||
I verified this for 1.9.0.5 when I verified bug 451709.
Keywords: fixed1.9.0.5 → verified1.9.0.5
You need to log in
before you can comment on or make changes to this bug.
Description
•