variables changing erratically.

[Drac]

At strange times variables within a vector I've made will change. Some examples of "strange times" are returning true from a function, and allocating things that have nothing to do with anything, for an example you can look at these screen shots taken during debugging.

http://img294.imageshack.us/img294/3061/captureec8.jpg
http://img214.imageshack.us/img214/972/capture2bq6.jpg

My question is if anybody has any idea why or how this would happen, because I don't. My project has no warnings up until level3 at which point a whole bunch of headers I include put out deprecated function warnings.

Any ideas will help, because as I have said, I don't have any. I can give more information on request.

[Daved]

Can you point out what we should be looking at?

Sometimes debug displays change because not all values shown in the debugger are valid and being used by the vector (or whatever object). Does your vector have bad data if you actually access it through code?

[Drac]

The data is screwed up if I try to access it, and causes crashes. I was trying to find out where it got screwed up and I can't seem to find out because it changes every couple lines seemingly randomly (though consistently between runs). And it gets changed to completely invalid data.

[Daved]

My guess would be that the BlobManager instance is messed up or you've corrupted the heap somehow. Are you using new/delete in your code? Perhaps deleting something you shouldn't be deleting?

[Salem]

So what does
new int;
do, apart from waste some memory?

> My project has no warnings up until level3 at which point a whole bunch of headers I include put out deprecated function warnings.
Such as?
You can selectively turn off warnings you know.

Besides, no warnings doesn't mean you're free to stop thinking about issues. Plenty of valid programs will pass every diagnostic you could ever apply, but will quite happily crash.

Some debuggers enable you to access the hardware breakpoint registers. Use these to trap writes to memory locations which you think should not be changed.

[Drac]

So what does
new int;
do, apart from waste some memory?

It shouldn't do anything else, but the debugger makes it look like it's changing the values. I'm just using it to eliminate variables, I used to allocate another object there and I wanted to make sure it wasn't something wrong with that.

Besides, no warnings doesn't mean you're free to stop thinking about issues. Plenty of valid programs will pass every diagnostic you could ever apply, but will quite happily crash.

Yeah, I just figured I would throw that in.

Some debuggers enable you to access the hardware breakpoint registers. Use these to trap writes to memory locations which you think should not be changed.

I'll look into that, it should help.

Perhaps deleting something you shouldn't be deleting?

That seems to be the most likely, then the new int could be put into it's place. I use new and delete every once and a while, I'll double check all the places I use it.

I think I've got a place to start from between the hardware breakpoint business, and checking my memory management. I'll let you guys know how that goes.