[SERVER-12374] Windows dumps have corrupted CONTEXT_RECORD Created: 15/Jan/14  Updated: 11/Jul/16  Resolved: 24/Jan/14

Status: Closed
Project: Core Server
Component/s: Diagnostics
Affects Version/s: 2.5.5
Fix Version/s: 2.5.5

Type: Bug Priority: Major - P3
Reporter: Mark Benvenuto Assignee: Mark Benvenuto
Resolution: Done Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified
Environment:

Windows


Issue Links:
Depends
is depended on by SERVER-12313 mongod produces an access violation o... Closed
Backwards Compatibility: Fully Compatible
Operating System: Windows
Participants:

 Description   

When we hit an exception in Windows, we get a CONTEXT_RECORD. We then pass this context record to the DBGHelp to print the stack trace. DbgHelp mutates the CONTEXT_RECORD, but we pass the now mutated CONTEXT_RECORD which points to the bottom of the stack instead of the top the stack where the A/V occurs to MiniDumpWriteMinidump. As a result, we get a minidump that points to the wrong place, and is not useful for debugging windows issues.



 Comments   
Comment by Githook User [ 22/Jan/14 ]

Author:

{u'username': u'markbenvenuto', u'name': u'Mark Benvenuto', u'email': u'mark.benvenuto@mongodb.com'}

Message: SERVER-12374: Windows dumps have corrupted CONTEXT_RECORD
Branch: master
https://github.com/mongodb/mongo/commit/82146730b9eb94e9e97f2c913b5844151f7001cb

Generated at Thu Feb 08 03:28:22 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.