Re: Debug library crashes when linked with Release build

Tech Tip: Click here to run a free scan for Windows Errors and optimize PC performance

On Apr 9, 12:44 pm, Dave Johansen <davejohan...@xxxxxxxxx> wrote:
On Apr 8, 3:45 pm, Dave Johansen <davejohan...@xxxxxxxxx> wrote:



On Apr 8, 3:33 pm, "Ben Voigt [C++ MVP]" <r...@xxxxxxxxxxxxx> wrote:

Dave Johansen wrote:
On Apr 8, 2:52 am, Ismo Salonen <Ismo.Salo...@xxxxxxxxx> wrote:
--snip--

It does no more work because some classes have different sizes in
debug vs. release mode. In debug mode ( _DEBUG defined) the classes
contains extra fields for runtime checks. When release mode is
compiled the classes memory footprint is smaller thanm in debug mode
and debug mode writes memory locaations it should not ( those, now
nonexistent debug variables).

This worked in 2003 because it did not have such sophisticated debug
helpers ( e.g iterator debugging). Using such combination
(debug&release) in same executable was never supported, it worked by
pure luck (or if you *really* knew what to do) .

br
ismo

I think that the claim that it "worked by pure luck" is not correct.
It worked because there's no standard compliant reason why it
shouldn't. I understand that the debug mode now supports more advanced

You can't hide behind the standard here, because you defined _DEBUG, which
begins with underscore+capital letter and as such is reserved for the
compiler or library implementation. When you start messing with reserved
identifiers you are completely implementation-dependent.

Beyond that, the standard requires that the one-definition rule be
respected. Frequently this requires having the same macro definitions
across the whole project, including static libraries, because although ODR
doesn't apply to macros, macros control the definitions of other things.

checks and such, but there's no reason that this couldn't have been
done without maintain existing features (an additional preprocessor
directive that allowed the additional checks to be disable would have
solved the problem). I understand why things broke and the change
makes sense from a certain perspective, but claiming that it "has to
be that way" just isn't true.

I believe there are other macros (why would you need a new directive???)
that control the extra checks.

Dave

I agree 100% and I understand why things are the way they are, but I
still believe that they are this way by choice and not by some
external, uncontrollable force. The versions of Visual Studio prior to
2005 stand as a testament to this, because what I am trying to do was
allowed and functioned properly before Visual Studio 2005. I also
agree 100% that mixing debug and release libraries isn't recommended,
but that doesn't mean that it should be impossible.
Dave

I did a little more digging and it turns out that the iterator
debugging stuff can be disabled (which fixes the problem I was having)
by defining _HAS_ITERATOR_DEBUGGING as 0. You can read more about it
here:http://msdn2.microsoft.com/en-us/library/aa985939(VS.80).aspx

Thanks everyone for all of the help and advice,
Dave

I would like to make a correction and state that turning off the
iterator debugging didn't fix all of the problems that I was having
with mixing debug and release builds, so I guess that this is just a
semi-undocumented breaking change for Visual Studio 2005.

Dave
.

Relevant Pages

  • Re: Execution time debug vs. release
    ... debugging features that have been added in VS2005 C++ compiler. ... but when compiled in debug mode takes almost 40 seconds with 100% CPU ... speed with Task Manager showing 0% CPU time. ...
    (microsoft.public.vc.mfc)
  • Re: How do i debug in Release mode
    ... You can turn debugging on or ... down compiler bugs or subtleties that don't appear when in Debug mode. ...
    (comp.lang.cpp)
  • Re: CPtrArray Performance
    ... CPtrArray has approximately the same performance as an ordinary array. ... are you measuring debug or optimized code? ... can completely swamp the actual function execution. ... In debug mode, you worry about getting it right. ...
    (microsoft.public.vc.mfc)
  • Re: Issue using encryption in Debug/Release mode ??
    ... we have encrypted files with the DEBUG version of KEM.dll ... invoked in debug mode, introduces code errors. ... Another subtle issue is that it is very easy to set different compiler ...
    (sci.crypt)
  • Re: Debug library crashes when linked with Release build
    ... In debug mode the classes ... compiled the classes memory footprint is smaller thanm in debug mode ... compiler or library implementation. ...
    (microsoft.public.dotnet.languages.vc)