Closed Bug 522600 Opened 15 years ago Closed 15 years ago

SkipList stack frames with 0x\d{1} should be skipped for signature (except 0x0)

Categories

(Socorro :: General, task)

task
Not set
normal

Tracking

(Not tracked)

RESOLVED FIXED

People

(Reporter: ted, Assigned: griswolf)

References

()

Details

I pointed this out to lars on IRC the other day, and he agreed it was a bug, but had to think about how to fix it. Just noticed we have a bunch of reports with signature @0x1 in the production db, so we should get this fixed.
it should be clear that we're talking about n for n <= 1024 (or some similar number)
I meant exactly one single digit.
Summary: stack frames with 0xN should be skipped for signature → stack frames with 0x\d{1} should be skipped for signature
Will be handled with bug #511758
we have a mandate all the way back to the beginning to treat @0x0 as a prefix signature. Ted, is this a rescission of that mandate?
No, I think whatever we're currently doing with 0x0 should stay the same, but I noticed that we also have crashes @0x1, and they wind up with a signature of "0x1", which seems wrong.
Summary: stack frames with 0x\d{1} should be skipped for signature → stack frames with 0x\d{1} should be skipped for signature (except 0x0)
Also want to clarify: Is this \d (decimal digit) or [1-9a-fA-F] (choosing the '1' in a semi-arbitrary way)
Hex, yes. My attempt to ultra-clarify in the bug title clearly failed.
Summary: stack frames with 0x\d{1} should be skipped for signature (except 0x0) → SkipList stack frames with 0x\d{1} should be skipped for signature (except 0x0)
Assignee: nobody → griswolf
Resolved per bug 529076 2009-11-18 16:07:48 PST
Status: NEW → RESOLVED
Closed: 15 years ago
Resolution: --- → FIXED
Component: Socorro → General
Product: Webtools → Socorro
You need to log in before you can comment on or make changes to this bug.