First-chance exception at 0×7c812a5b in : Microsoft C++ exception: CError at memory location
If you are programming and you have some calls to ShellExceute in your code, and you are debugging, you might see this fly across the output window
First-chance exception at 0×7c812a5b in
The app will be your exe name, and location will be a memory location.
You can reproduce this by calling ShellExecute with a url as the file param like so:
ShellExecute(NULL, “open”, “http://www.stevienova.com” , NULL, NULL, SW_SHOWNORMAL);
You should have a path to a file, but what Windows does is look for the http:// or .com and then does a lookup in the registry for the default handler, which more than likely is Internet Explorer, or Firefox, or whatever is your default browser. More info here
INFO: Use ShellExecute to Launch the Default Web Browser KB 224816
I haven’t tried catching the exception, but I can’t figure out a way to get rid of it. It doesn’t seem to hurt anything and actually doesn’t throw up an error. Just an annoying little quirk in Windows and C++.
I did a little digging on Google and didn’t seem to find any more info, so I guess it isn’t a huge deal. Ahh, the mystery of Windows!!!
Simlar Posts
March 10th, 2007 at 11:30 am
This one isn’t much of a mystery. The output window tells you when anything happens (a library is loaded, an exception happens, whatever). But what it tells doesn’t necessarily mean there’s a problem. In this case, what’s happening is that an exception is being raised and caught. The output window tells you about the exception being raised, and the fact that the app doesn’t crash tells you that it’s being caught and handled.
March 10th, 2007 at 11:32 am
the mystery is, what is the exception and why does it occur and why only when I call a URL?
March 10th, 2007 at 1:25 pm
I think the exception is a CError (looks that way from the output you pasted), and as for why, it’s probably an internal exception that they use for logic flow control (but that’s just guess work).