hansw77041
asked on
Uncaught exception in WindowProc (returning 0).
I'm using VC6 and can't figure out how to get the debugger to stop on this error.
Warning: constructing COleException, scode = DISP_E_BADINDEX ($8002000B).
First-chance exception in test.exe (KERNEL32.DLL): 0xE06D7363: Microsoft C++ Exception.
This line sometimes shows up on the same error.
Warning: Uncaught exception in WindowProc (returning 0).
Is it possible to get the debugger to stop on an error like this if so how ?
Warning: constructing COleException, scode = DISP_E_BADINDEX ($8002000B).
First-chance exception in test.exe (KERNEL32.DLL): 0xE06D7363: Microsoft C++ Exception.
This line sometimes shows up on the same error.
Warning: Uncaught exception in WindowProc (returning 0).
Is it possible to get the debugger to stop on an error like this if so how ?
SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
KurtVon:
Yes to catch the exception is what my question is all about. but how to do that ? As humakumar implies it is not possible.
The initialization is correct, I think the biggest problem is that all happened to working code when I upgraded from Version 6 to Version 7 !
I'm sick of companies peddling libraries and programs as if it's tested, just for me and others to become their beta tester.
It's getting so bad I'm at the point of dumping Version 7 and going back to Version 6 which does not have these problems. V6 has plenty of crap in it, but that this killer.
jkr: Yes I did that and of course it points to a fuction within the library, and that's as far as I can go without source.
To All:
Everyone has contributed so I'm splitting points, dividing 500 by 3 is not easy so please accept my split.
Yes to catch the exception is what my question is all about. but how to do that ? As humakumar implies it is not possible.
The initialization is correct, I think the biggest problem is that all happened to working code when I upgraded from Version 6 to Version 7 !
I'm sick of companies peddling libraries and programs as if it's tested, just for me and others to become their beta tester.
It's getting so bad I'm at the point of dumping Version 7 and going back to Version 6 which does not have these problems. V6 has plenty of crap in it, but that this killer.
jkr: Yes I did that and of course it points to a fuction within the library, and that's as far as I can go without source.
To All:
Everyone has contributed so I'm splitting points, dividing 500 by 3 is not easy so please accept my split.
>>Yes to catch the exception is what my question is all about. but how to do that ?
Write your own exception filter and set that via 'SetUnhandledExceptionFilt
Write your own exception filter and set that via 'SetUnhandledExceptionFilt
ASKER
At first I thought is could be my code, and then coded a bunch of stuff to ensure arrays are not used beyond the correct size.
I'll leave the question open for a while to see if someone else has any suggestion.