slightly puzzled...

l a u r e n

i am getting a bunch of these warning messages after my OnInitDialog() exits: First-chance exception in 8028c.exe (KERNEL32.DLL): 0xC0000005: Access Violation. and i have absolutely no idea why ... i traced it down into the depths of wincore.cpp and its friends but god only knows what they get up to when they're bored ... thing is my app doesn't go squiff even in release mode so i'm a wondering if its something i can ignore or should i be afraid ... very afraid :confused:

"... and so i said to him ... if it can't dance and you can't eat it either f**k it or throw it away"
8028finder.com

Henk Groenewoud

What does your code look like. It sounds like an initialization problem.

Roger Allen

Do you have an ActiveX control on your dialog? I get these when I have an in-house ActiveX control in use. I think the windows system is trying to access a default function that is not present or some such. Doesn't seem to affect how my program works. Roger Allen Sonork 100.10016 If I had a quote, it would be a very good one.

Jonathan Craig

I found this article in the MSDN: INFO: First and Second Chance Exception Handling Q105675 It explains what you are seeing. There are many DLLs (and other code) that throw exceptions on purpose to see if things are valid. I have used this technique to check if memory-mapped files have real memory allocated for them. From the article, the debugger sees these exceptions before the application does. It creates a warning before a handler is able to catch the exception. Note that they must be getting handled or your application would crash. I see them also in most of my applications and they are safe. I have written hundreds of applications and never seen these messages to be a problem. Hope this helps...:) Jonathan Craig www.mcw-tech.com

l a u r e n

awesome thanks for the info i wondered why my release build wasnt dying at the very least :-D

"... and so i said to him ... if it can't dance and you can't eat it either f**k it or throw it away"
8028finder.com