WxHaskell/Development/Debugging

The printable version is no longer supported and may have rendering errors. Please update your browser bookmarks and please use the default browser print function instead.

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).

Exception code 0xC0000005

Access violation, also called General Protection Fault. May indicate an API incompatibility.

Exception code 0xC000007B

If you get an exception code 0xC000007B immediately after starting your wxHaskell program, there is a mismatch between the bitness of your program and the bitness of the wxWidgets DLLs. Note, that the package wxc checks the bitness at installation time, but things can go wrong afterwards, like changing the search path to point to a different version of the wxWidgets DLLs.

Exception code 0xC0000139

Procedure entry point not found in DLL; it is unknown why this sometimes happens, but might be resolved by cleaning up intermediate files from the compiler and compiling everything again.