forums.silverfrost.com

KennyT · Joined: 02 Aug 2005 Posts: 320

Something has just started happening that I can't seem to isolate. I can build and run my main application fine, but when I try to run it under the debugger, I get an exception C0000235, with no stack to track back.

I can trace close to where it's occurring, by setting a break at a particular CALL statement, but if I try to run to that point using F3, it crashes before getting there (so I think the breakpoint I was "aiming for" is probably a red herring? - it's code that hasn't changed in weeks)

Anyone else come across this?

I am still running v5.5. I tried v6 but some unrelated code crashes the compiler, so I went back to 5.5...

K

KennyT · Joined: 02 Aug 2005 Posts: 320

Bit more info...

If I edit the SDBG.INI file and set:

IgnoreException-3=C0000235

When I then run SDBG I get a window popup saying "Catastrophic failure"!

K

KennyT · Joined: 02 Aug 2005 Posts: 320

Some more info...

I've copied my entire development structure over to another machine (windows7 as it happens) and the problem does not occur. So, it's something specific on my laptop.

I have run a malware scan and found a few trojans which have been removed to no avail.

I will run a full virus scan and see what that throws up.

But I guess the debugger itself is off the hook for the moment.

K

silverfrost · Posted: Sun Dec 12, 2010 1:47 pm Post subject:

"Catastrophic failure", you have to love error messages that overstate the issue Smile

It sounds like a driver issue because that error number is in the kernel space. Any new drivers or hardware recently?

KennyT · Joined: 02 Aug 2005 Posts: 320

Not knowingly. I'll see if I can do a "rollback"...

K

KennyT · Joined: 02 Aug 2005 Posts: 320

OK, rolling back to the last system restore point (which was just an automatic one, not described as being in response to a new driver install)...
.
.
.
.
has fixed it!

Very Happy

Thanks.

K

KennyT · Joined: 02 Aug 2005 Posts: 320

Some more info.

The problem was actually caused by my virus checker (Avira). Somehow it had got its knickers in a twist!

Uninstalling and reinstalling the virus checker fixed it.

K

Sebastian · Joined: 20 Feb 2008 Posts: 177

This exception seems to be a "hint" from the antivirus software that a dangerous operation was encountered. Looking on the net reveals quite some pages that deal with debugging while the antivirus software is active resulting in problems (file/registry protection).