Jump to content

  • Log In with Google      Sign In   
  • Create Account


vector subscript out of range


Old topic!
Guest, the last post of this topic is over 60 days old and at this point you may not reply in this topic. If you wish to continue this conversation start a new topic.

  • You cannot reply to this topic
8 replies to this topic

#1 lride   Members   -  Reputation: 633

Like
0Likes
Like

Posted 08 December 2012 - 11:48 AM

I have a vector of pointer to entity. I also have a GameWorld class that contains this vector.
[source lang="cpp"]std::vector<Entity*> entities;GameWorld::GameWorld(){ entities.push_back(new Character("YOURS", CharacterType::BLACK));}GameWorld::~GameWorld(){ for(auto e: entities) delete e;}[/source]

When I close the game I get assertion failure "vector subscript out of range". What did I do wrong?

Edit:
I still get the vector assertion failure even when I changed the std::vector to std::list
I also found out that I can use the std::vector even I don't #include <vector>

OK I solved my problem. The GameWorld object is inside Game class which is a singleton. So the GameWorld is statically allocated.
But when I allocated Game class on stack, it worked fine. I have no idea why..

Edited by lride, 08 December 2012 - 01:20 PM.

An invisible text.

Sponsor:

#2 MarkS   Prime Members   -  Reputation: 882

Like
0Likes
Like

Posted 08 December 2012 - 01:51 PM

Why not use "delete entities;"? The vector destructor takes care of calling the Entity destructor for each object in the list..

#3 Radikalizm   Crossbones+   -  Reputation: 2825

Like
3Likes
Like

Posted 08 December 2012 - 02:03 PM

Why not use "delete entities;"? The vector destructor takes care of calling the Entity destructor for each object in the list..


The vector will destroy the pointers, but not the objects the pointers are pointing to. Big difference!
Also 'delete entities' wouldn't even work as the entities vector wasn't allocated on the heap. It wouldn't even compile either, as entities is not a pointer type.

I gets all your texture budgets!


#4 MarkS   Prime Members   -  Reputation: 882

Like
0Likes
Like

Posted 08 December 2012 - 02:16 PM

I see. He is creating a vector of Entity pointers, not a pointer to a vector of Entity objects.

Edited by MarkS, 08 December 2012 - 02:17 PM.


#5 lride   Members   -  Reputation: 633

Like
0Likes
Like

Posted 08 December 2012 - 02:18 PM

Anyways getting rid of evil singleton design solved the problem
An invisible text.

#6 Radikalizm   Crossbones+   -  Reputation: 2825

Like
2Likes
Like

Posted 08 December 2012 - 02:20 PM

Still, doesn't the vector destructor call the object's destructor upon deletion?


A vector does call a destructor for an object it holds when that object is erased, but this vector is storing pointer objects, not Entity objects.
So basically the vector is calling a destructor for the pointer object (which is perfectly legal), but that doesn't mean the destructor for the object the pointer is pointing to gets called or that the memory consumed by the object the pointer is pointing to gets released.

Edited by Radikalizm, 08 December 2012 - 02:20 PM.

I gets all your texture budgets!


#7 MarkS   Prime Members   -  Reputation: 882

Like
0Likes
Like

Posted 08 December 2012 - 04:20 PM


Still, doesn't the vector destructor call the object's destructor upon deletion?


A vector does call a destructor for an object it holds when that object is erased, but this vector is storing pointer objects, not Entity objects.
So basically the vector is calling a destructor for the pointer object (which is perfectly legal), but that doesn't mean the destructor for the object the pointer is pointing to gets called or that the memory consumed by the object the pointer is pointing to gets released.


That is very interesting! I don't create vectors of pointers, but I'll need to keep that in mind.

Since we are on the subject, why create a vector of pointers in the first place?

#8 iMalc   Crossbones+   -  Reputation: 2299

Like
0Likes
Like

Posted 08 December 2012 - 04:44 PM

When I close the game I get assertion failure "vector subscript out of range". What did I do wrong?

You either corrupted your vector somewhere, or you tried to access outside of its bounds.

Edit:
I still get the vector assertion failure even when I changed the std::vector to std::list
I also found out that I can use the std::vector even I don't #include <vector>

Both of those statements are inaccurate.
If you change it to a list then you wont get assert about the vector because it isn't a vector any more. A std::list does not use code from within the std::vector. You're probably just getting the same error from a different piece of the std library. Getting the same behviour probably means that you are going past the end of the container rather than corrupting it.
If code with vector still compiles, then something else you are including is pulling in the vector header for you. You should probably not be relying on that.

If you need your vector to hold pointers for reasons of polymorphism, then you might be better off with a boost ptr_container rather than a vector. Otherwise you should problably just store instances directly rather than pointers.

Edited by iMalc, 08 December 2012 - 04:46 PM.

"In order to understand recursion, you must first understand recursion."
My website dedicated to sorting algorithms

#9 lride   Members   -  Reputation: 633

Like
0Likes
Like

Posted 08 December 2012 - 05:30 PM

Since we are on the subject, why create a vector of pointers in the first place?

Because I want to store different kinds of object in the same vector. This can only be done by storing the pointers or references to the object and using polymorphism.
Also, I store pointers to objects in a vector when the object is too expensive to copy. (When you use std::vector::push_back(), the copy of the object gets stored.)
However, this extra copy can be avoided by using c++11 'move', .


Both of those statements are inaccurate.
If you change it to a list then you wont get assert about the vector because it isn't a vector any more. A std::list does not use code from within the std::vector. You're probably just getting the same error from a different piece of the std library. Getting the same behviour probably means that you are going past the end of the container rather than corrupting it.
If code with vector still compiles, then something else you are including is pulling in the vector header for you. You should probably not be relying on that.

If you need your vector to hold pointers for reasons of polymorphism, then you might be better off with a boost ptr_container rather than a vector. Otherwise you should problably just store instances directly rather than pointers.


This is the only place I'm using vector in my entire project. and I've searched #include <vector> in my entire solution and there was none.
But now that I already solved the problem, what is the advantage of using a boost ptr vector instead of using a normal vector

Edited by lride, 08 December 2012 - 05:50 PM.

An invisible text.




Old topic!
Guest, the last post of this topic is over 60 days old and at this point you may not reply in this topic. If you wish to continue this conversation start a new topic.



PARTNERS