Prev: Any one got the solution for changing wallpaper
Next: change a wall paper in Pocketpc
From: Timothy Dean on 25 Jun 2008 19:15
I have a WM 5 application written in C++ / MFC using VS 2005. When error
reporting is turned off, everything runs great. When error reporting is
turned on, there is a particular place in the app where an error pops up
with the Send / Don't send option. If you close this window, the app
continues on just fine. When I look at the details of the error, it says
the EvntType is WinCE501bException. When I run it in debug mode, the
debugger doesn't catch any exceptions. Whats the best way to proceed to try
to track this error down? Why doesn't the debugger catch it? What is a
WinCE501bException? Thanks.

Timothy Dean


From: patrickdekleijn on 10 Jul 2008 19:27
I've had the WinCE501bException (netcfag12_0.dll) trying to parse an
invalid bitmap resource to a control. Unfortunately the exception is
not caught by the debugger, leaving us somewhat clueless about what
went wrong. The application exits and NET Framework notifies the user
that is did unexpected.


> Whats the best way to proceed to try to track this error down?

Although the debugger gets detached from the application's thread
before it can detect the exception you can use the debugger to track
down what instructions were executed that generated the exception. Try
debugging your application with Debug > Step Into (F11) from the start
or before the particular part of your application is about to fail.
Follow all code step by step until your code breaks the app. The last
line you hit with the debugger invoked the crash.

Patrick de Kleijn
 | 
Pages: 1
Prev: Any one got the solution for changing wallpaper
Next: change a wall paper in Pocketpc