Closed
Bug 1341035
Opened 7 years ago
Closed 7 years ago
Add MOZ_CrashOOL and MOZ_CrashPrintf to the prefix signature list
Categories
(Socorro :: Infra, task)
Socorro
Infra
Tracking
(Not tracked)
RESOLVED
FIXED
People
(Reporter: ehoogeveen, Unassigned)
References
Details
In bug 1338574 I'm adding two new variants of MOZ_CRASH, each with its own function. IIUC, these will need to be added to the prefix signature list at [1] so we don't group all crashes utilizing these functions together. I'm not sure which way around the dependency should be here, but I'm setting this to block bug 1338574 for now. [1] https://github.com/mozilla/socorro/blob/master/socorro/siglists/prefix_signature_re.txt
Reporter | ||
Comment 1•7 years ago
|
||
Created a PR to do this at https://github.com/mozilla/socorro/pull/3673
Comment 2•7 years ago
|
||
Just to be sure, you want those signatures to be part of the signature, but to always show at least the one frame that is after it, right? With your patch, that's what will happen. I ask because in 1338574#c30 you mention you want Socorro to "ignore" them, so I'd rather be sure the right thing is done. :)
Reporter | ||
Comment 3•7 years ago
|
||
Yeah, I think that would be ideal. Omitting them altogether probably wouldn't be bad either, but if a particular function has both regular MOZ_CRASHes and one of these, this makes them slightly easier to distinguish at a glance.
Reporter | ||
Comment 4•7 years ago
|
||
Though (sorry about the noise) if signature length becomes a problem, we should probably omit them instead.
Comment 5•7 years ago
|
||
Signatures get truncated at 255 bytes. I'm not sure if that knowledge helps here or not.
Comment 6•7 years ago
|
||
If signature length becomes a problem, we can file a new bug and find solutions. For now, let's just proceed with this. https://github.com/mozilla/socorro/commit/19efcc961c69cbc9095cdf2dad41c89f4033f628
Status: NEW → RESOLVED
Closed: 7 years ago
Resolution: --- → FIXED
Reporter | ||
Comment 7•7 years ago
|
||
Great, thanks!
You need to log in
before you can comment on or make changes to this bug.
Description
•