[SERVER-7352] Do not try to exit cleanly after unhandled exception in Windows Created: 14/Oct/12 Updated: 11/Jul/16 Resolved: 15/Oct/12 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Internal Code |
| Affects Version/s: | 2.2.0 |
| Fix Version/s: | 2.2.2, 2.3.0 |
| Type: | Bug | 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 |
| Operating System: | Windows |
| Participants: |
| Description |
|
The current code for unhandled exceptions in Windows calls dbexit(EXIT_UNCAUGHT, "unhandled exception") in release builds. It passes the exception on to the default handler in debug builds. It should do what we do on other platforms and call ::_exit(EXIT_ABRUPT) in both release and debug builds. |
| Comments |
| Comment by auto [ 06/Nov/12 ] |
|
Author: {u'date': u'2012-10-14T21:25:02Z', u'email': u'tad@10gen.com', u'name': u'Tad Marshall'}Message: In Windows, exit after an access violation the same way we exit on other |
| Comment by auto [ 01/Nov/12 ] |
|
Author: {u'date': u'2012-11-01T14:55:26Z', u'email': u'randolph@10gen.com', u'name': u'Randolph Tan'}Message: |
| Comment by auto [ 15/Oct/12 ] |
|
Author: {u'date': u'2012-10-14T14:25:02-07:00', u'name': u'Tad Marshall', u'email': u'tad@10gen.com'}Message: In Windows, exit after an access violation the same way we exit on other |