Difference between revisions of "WxHaskell/Development/Debugging"
< WxHaskell | Development
Jump to navigation
Jump to search
(Created page with "{{Stub}} Some tips on debugging == Windows == === Crashes === When your wxHaskell program crashes, look in the [http://maximumpcguides.com/windows-7/how-to-check-system-...") |
(Added Category:wxHaskell) |
||
| Line 14: | Line 14: | ||
This code indicates that a debug message is written, probably by wxWidgets. Run your wxHaskell program in the [https://www.gnu.org/software/gdb/ GNU debugger] to see the debug message(s). |
This code indicates that a debug message is written, probably by wxWidgets. Run your wxHaskell program in the [https://www.gnu.org/software/gdb/ GNU debugger] to see the debug message(s). |
||
| + | |||
| + | |||
| + | [[Category:wxHaskell]] |
||
Revision as of 17:59, 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. 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).