[SERVER-5193] Enhance Windows unhandled exception filter reporting Created: 04/Mar/12  Updated: 11/Jul/16  Resolved: 19/Apr/12

Status: Closed
Project: Core Server
Component/s: Logging, Stability, Testing Infrastructure
Affects Version/s: None
Fix Version/s: 2.1.1

Type: Improvement Priority: Major - P3
Reporter: Tad Marshall Assignee: Tad Marshall
Resolution: Done Votes: 0
Labels: Windows
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified
Environment:

Windows


Backwards Compatibility: Fully Compatible
Participants:

 Description   

The information passed to the unhandled exception filter in Windows when an access violation (segfault) occurs includes the address that was being referenced by the offending instruction and whether this was a read or a write and whether or not DEP (Data Execution Prevention) triggered the exception. We should include this information in our log of the access violation along with the address of the offending instruction that we are already logging.



 Comments   
Comment by auto [ 19/Apr/12 ]

Author:

{u'login': u'tadmarshall', u'name': u'Tad Marshall', u'email': u'tad@10gen.com'}

Message: SERVER-5193 Display Windows access violation type and address
Branch: master
https://github.com/mongodb/mongo/commit/a96ec246c847beb73afa7162c8187333119cd60f

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