Difference between revisions of "WxHaskell/Development/Debugging"
< WxHaskell | Development
Jump to navigation
Jump to search
(Added Category:wxHaskell) |
(→Crashes: Added link to NTSTATUS values page) |
||
| Line 9: | Line 9: | ||
=== Crashes === |
=== Crashes === |
||
| − | When your wxHaskell program crashes, look in the [http://maximumpcguides.com/windows-7/how-to-check-system-logs-in-the-event-viewer/ application audit log] for an error message and make a note of the exception code. |
+ | When your wxHaskell program crashes, look in the [http://maximumpcguides.com/windows-7/how-to-check-system-logs-in-the-event-viewer/ application audit log] for an error message and make a note of the exception code. Look at Microsoft's [https://msdn.microsoft.com/en-us/library/cc704588.aspx NTSTATUS values page], or use a search engine to find an explanation for this code. |
==== Exception code 0x40010006 ==== |
==== Exception code 0x40010006 ==== |
||
Revision as of 18:27, 24 February 2015
This article is a stub. You can help by expanding it.
Some tips on debugging
Windows
Crashes
When your wxHaskell program crashes, look in the application audit log for an error message and make a note of the exception code. Look at Microsoft's NTSTATUS values page, or use a search engine to find an explanation for this code.
Exception code 0x40010006
This code indicates that a debug message is written, probably by wxWidgets. Run your wxHaskell program in the GNU debugger to see the debug message(s).