Closed Bug 1280442 Opened 8 years ago Closed 8 years ago

Compare minidump memory with the matching binary (Windows)

Categories

(Socorro :: Backend, task)

Product:
Socorro
Component:
Backend
Type:
task
Priority:
Not set
Severity:
normal

Tracking

(Not tracked)

Status:
RESOLVED DUPLICATE of bug 1274628

People

(Reporter: benjamin, Unassigned)

References

(Blocks 1 open bug)

Details

When minidumps are submitted, we submit 512 bytes of space around the IP. We may also submit other pages which are suspicious.

We want to compare these to data that should have been loaded off disk from the original binaries and then relocated.

It may be that this is mismatched because of:

* function hooking (from 3rd-party)
* bad memory
* bad disk

In reporting, if there are mismatches we should highlight the particular disassembly situation (both original and modified) and show whether this is a one-bit flip or something else.

Ted, I know we talked about this but you didn't file it already, did you?
Flags: needinfo?(ted)
I can't recall ever filing this. We do have the original binaries in the symbol server for Windows nowadays. I don't know offhand how you compare accounting for relocations. I assume that's in the binary headers somewhere.
Flags: needinfo?(ted)
Oh, but dbaron filed bug 1274628.
Blocks: 1274628
Yeah, I've written that relocation code before: it's finicky but not that hard.
Yes, this is a dup of bug 1274628.
Status: NEW → RESOLVED
Closed: 8 years ago
Resolution: --- → DUPLICATE
You need to log in before you can comment on or make changes to this bug.