Surface the GetLastError() value in Windows minidumps
Categories
(Toolkit :: Crash Reporting, enhancement)
Tracking
()
Tracking | Status | |
---|---|---|
firefox88 | --- | fixed |
People
(Reporter: gsvelto, Assigned: Gankra)
References
Details
Attachments
(2 files)
:dmajor pointed out in bug 1688271 comment 5 that Windows minidumps taken from the nightly contain both the value that GetLastError() would return at the point the minidump was taken. When analyzing a minidump with windbg this value can be extracted via the !gle
command and it gets printed out both as a Win32 error and as the corresponding NTSTATUS value (IIUC). See the screenshot.
The value is stored in the TEB (bug 1688271 comment 7) whose address is stored in the minidump's thread information. We should modify the stack walker to extract it and print it out together with the rest of the stack-trace.
I'll file a separate bug to display it in Socorro's front-end.
Comment 1•3 years ago
|
||
I started tracking stackwalker issues here: https://github.com/mozilla-services/minidump-stackwalk/issues
Seems like this is specifically a stackwalker issue. Does that sound right?
We can keep this bug. I can write an issue in the minidump-stackwalk repo pointing here for details.
If the code ends up hardcoding the field offset (since the SDK's struct _TEB
is opaque), remember that it's architecture-dependent. 0x34 on 32-bit and 0x68 on 64-bit.
Assignee | ||
Updated•3 years ago
|
Assignee | ||
Comment 3•3 years ago
|
||
Pushed by abeingessner@mozilla.com: https://hg.mozilla.org/integration/autoland/rev/70904d6ca415 extract the GetLastError value from minidumps. r=gsvelto
Comment 5•3 years ago
|
||
bugherder |
Comment 6•3 years ago
|
||
I don't understand how this bug is a bug in the Socorro processor. Should it get moved somewhere else? Is there work we have to do in the Socorro processor?
Reporter | ||
Comment 7•3 years ago
|
||
I messed things up. This should be in crash reporting (gotta move it there) and I should file another one for the processor which will be about including this feature in Socorro's stackwalker.
Reporter | ||
Comment 8•3 years ago
|
||
Actually, I'm going to put the new bug directly on Socorro's stackwalker GitHub project because it makes more sense there.
Comment 9•3 years ago
|
||
Awesome--thank you!
Description
•