Re: strang behaviour std:vector and XString in VC6.0

From: John Harrison (john_andronicus_at_hotmail.com)
Date: 11/12/04


Date: Fri, 12 Nov 2004 12:41:39 -0000


"Stijn Oude Brunink" <soudebrunink@chello.nl> wrote in message
news:3Q1ld.1069$_u6.17@amsnews02.chello.com...
> Hello
>
> I'm using std:vector to hold some pointers
>
> vector<CBase*> x;
>
> In the debug version I've the following problem:
> After I've added a couple of pointers using the push_back function and I
> iterate over x the program crashes in the iteration loop. If I debug the
> program I see that the Iterator has som strange value which I did not put
> in. Finially I end up in the XString header where there seems to be some
> kind of memory allocation problem. If I ask for the last pointer in x
using
> x.back() I get a good result. but x[x.size()-1] produces nonsense;
>

You have a bug in your program. I can promise you that it is not in the
single line of code you have posted, but in one of the many lines of code
you didn't post.

> The problem stated does not occur in release mode.

That is not unusual, in fact it is typical. One possibility is that you have
an uninitialised variable which happens to get one value in debug mode and a
different value in release mode.

>
> Does anaybody know what is going on.
>

You have a bug in your code.

> I use VC6.0.
>

It has a very good debugger, use it. Alternatively post the code.

john



Relevant Pages

  • Re: strang behaviour std:vector and XString in VC6.0
    ... > In the debug version I've the following problem: ... > After I've added a couple of pointers using the push_back function and I ... > iterate over x the program crashes in the iteration loop. ... example of not more than 20 lines which uses no non-standard C++ ...
    (comp.lang.cpp)
  • strang behaviour std:vector and XString in VC6.0
    ... In the debug version I've the following problem: ... After I've added a couple of pointers using the push_back function and I ... iterate over x the program crashes in the iteration loop. ...
    (comp.lang.cpp)
  • Re: Release build seg faults at vector.push_back above certain size, b
    ... >i'm using a vectors of pointers in my code. ... >the whole thing get's really strange when i use the debug build. ... set the warning level to 4 and define ... deleteptr; ...
    (microsoft.public.dotnet.languages.vc)
  • Re: Setting pointer to null!
    ... debug builds do not and AFAIK have never done that. ... yourself and initialise it NULL on a release build. ... and I think they use a repeated 0xCD pattern. ... if you "defensively" initialize all pointers to ...
    (microsoft.public.vc.language)
  • Re: Passing Smart Pointers as Parameters
    ... How do you obtain interface pointers on your own object? ... It's not the problem with the interfaces on my object. ... debug output... ... should see the debug output, ...
    (microsoft.public.vc.atl)