Why does a Debug build fix an AV error?

[350Zed]

Hi,

My on going quest to rid an application of AV errors continues, and this is not helping my confusion.

One of the errors I have been looking into occurs when the main app calls a dll twice. The first time everything is fine the second time it fails.

Visual inspection of the code in both the main app and dll doesn't show any obvious errors so I built a debug version of the main app so I could trace through it, but this has fixed the problem!

Is compiling the debug version including something extra that is helping/masking the issue?

In the short term using the debug version is keeping the users quiet, but it's not an ideal solution and I'd like to get to the bottom of the original problem.

Thanks in advance.

 

[2ffat]

AV errors are notoriously difficult to debug. One reason is the cause you just reported. Perhaps the extra debug code is adding a delay allowing the stack to clear. It's very hard to say.

I would leave the debug version with your users until it is triggered with an AV and see where to go from there.

In the mean time, play with your original version and see if you can figure anything out.



James P. Cottingham
-----------------------------------------
[sup]I'm number 1,229!
I'm number 1,229![/sup]

 

[350Zed]

Thanks for the response James. Sounds like I need to go back to banging my head against the wall with this one! Joy.