Re: _HAS_ITERATOR_DEBUGGING won't stay = 0

From:

Vincent Finn <1@2.com>

Newsgroups:

microsoft.public.vc.language

Date:

Thu, 16 Nov 2006 12:08:06 +0000

Message-ID:

<bukol21e5m4nksgt5c29i62fc8o3geqop8@4ax.com>

On Tue, 14 Nov 2006 18:18:10 +0000, "Tom Widmer [VC++ MVP]"
<tom_usenet@hotmail.com> wrote:

Vincent Finn wrote:

Hi,

I am having a weird problem.

I have several projects building to static libs, I have one project
including them and building to a dll (managed).

In the project settings of every project I set
_HAS_ITERATOR_DEBUGGING=0

I get an assert in a call to vector<string>::clear().
"vector iterators incompatible" thrown from _Compat()
_Compat() is wrapped in "#if _HAS_ITERATOR_DEBUGGING".
I don't know how it is being called!

I have seen this assert when one of the projects didn't have
"_HAS_ITERATOR_DEBUGGING=0" but that isn't the case here.

For testing purposes I put
int i = _HAS_ITERATOR_DEBUGGING;
if (i == 0)
{
myVector.clear();
}

It will call clear() and assert!

Anyone seen anything like this?
Any suggestion on how to diagnose it further?

I am at a loss!

It sounds like it might be UB due to violation of the one definition
rule, where you have multiple different instantiations of
vector<string>, at least one compiled with _HAS_ITERATOR_DEBUGGING 1.
Perhaps you could search the .lib symbol tables for this _Compat
function to see which one is the culprit.

Tom

Thanks for that, it didn't appear in the libs but did show up in the
map file.

The managed lib was referencing the function it seemed to be ignoring
the project setting, once I defined it in the precompiled header it
stopped referencing it.

Unfortunately two 3rd party libs reference it so it still doesn't
work.

Oh well, I can work around it for now and rebuild the 3rd party libs
when I have more time.

Thanks for the suggestion, at least I know what the problem is now.

Vin