Weird first chance exceptions with STL vectors in C++
- Thread starter K.I.L.E.R
- Start date
K.I.L.E.R said:
Basically you're writing to either uninitialised or free'd memory. Most likely culprit is a bad list *, but your code fragment is far from exhaustive.
I don't remember which way round MS's default sentinel fills are. BAADF011 is one of them. In none release builds memory is filled when it's allocated, or freed.
Gizz, I originally wrote details in my first message, but I must have done something wrong since they aren't here 
I mean that you might be calling a function on a NULL or invalid pointer.
Your " vector<Spatial> *list;" is never newed in your code sample, if you want to use it without newing it, then just write "vector<Spatial> list;", it'll be automatically allocated on object creation.
While I'm at it:
I mean that you might be calling a function on a NULL or invalid pointer.
Your " vector<Spatial> *list;" is never newed in your code sample, if you want to use it without newing it, then just write "vector<Spatial> list;", it'll be automatically allocated on object creation.
While I'm at it:
Code:
private:
vector<Spatial> list; //you most likely want to give it a REAL name :p
public:
ObjectHolder(void)
{
list->push_back( Spatial() ); //not a dramatic change but if you do nothing with it...
}Captain Chickenpants
Regular
Probably generated by an assert in whatever library you are using.K.I.L.E.R said:
Something that is worth doing is looking at the call stack in your debugger (an often under used feature), have a look at the line that is going wrong.
It will almost certainly be accessing an invalid pointer.
Look at where is that pointer setup, check to see if something is corrupting the pointer.
Basically you want to track down the cause of the assertion by a process of elimination.
CC
Thanks. I have a new love for Java (Even C isn't this bad). 
I found the problem, it's when I add things into my list.
Problem solved.
It's probably going to give me diarrhea.
My Spatial class had it's "Point" as a pointer instead of a reference.
What this meant was that whenever my variable went out of scope it would call "delete".
I found the problem, it's when I add things into my list.
Problem solved.
It's probably going to give me diarrhea.
My Spatial class had it's "Point" as a pointer instead of a reference.
What this meant was that whenever my variable went out of scope it would call "delete".
Saem said:
Of course the design of C++ has a lot to do with compatibility with C, and that's probably the most important reason why C++ is popular (heavily used by many). I think that if C++ does not have to be compatible with C, it may have better syntax. However, even with a better syntax, a language this powerful is still likely to be dangerous. C++ in its current form is dangerous even to beginners who don't use its advanced functions (actually, mostly dangerous to C users since they tend to have false assumptions on C++). A better language design should be more safe to beginners, but I think current C++ almost have that if the beginner knows some simple rules (like avoiding pointers).
Unfortunately, current development directions of C++ is still going to a more advanced way, as in TR1. Beginners can use these cool new developments without complete understanding, but they (and sometimes even professional programmers) will eventually be bitten by the lack of some knowledge.
pcchen,
I think a language can be as powerful as one wants and it's fine. Look people operate very dangerous heavy machinery all the time and the reason it works out well most of the time is that a lot of effort has gone into making sure the operator knows what they're doing and the interface to it doesn't suck -- read, not a mine field of gotchas.
I think a language can be as powerful as one wants and it's fine. Look people operate very dangerous heavy machinery all the time and the reason it works out well most of the time is that a lot of effort has gone into making sure the operator knows what they're doing and the interface to it doesn't suck -- read, not a mine field of gotchas.