Problem with boost::shared_ptr

Recommended Posts

For a game, I want to have a bunch of enemies which can be divided by type (ie. there are thousands of them but only - say - ten classes, for example gunner, grenadier, tank etc.) - so my approach to implement this in a memory-efficient way is the following: The Approach/Set-Up I have a global model structure for each class, like this:
// global scope

Then there's a function that is called when the game starts that loads these models:
// on game start
{
}

Next I have a class called 'Enemy' which includes all kinds of stuff such as a position, rotation, ammunition, whatever, and a pointer to a model:
class Enemy
{
public:
boost::shared_ptr<Model>	model;
//Vector3			Position;
// etc.
};

Now I define a global std::list of my Enemy class:
// global scope again
std::list<Enemy> enemy;

The Problem I use the following function for adding a new enemy to the vector:
void AddEnemy ( EnemyType type )
{
Enemy _enemy;

if ( type == Gunner )
_enemy.model.reset ( &gunner_model );
else if ( type == Grenadier )
else if ( type == Tank )
_enemy.model.reset ( &tank_model );

enemy.push_back ( _enemy );

Console::Print ( "Enemy added   - new enemy count: %d", enemy.size ( ) );
}

And this one to get rid of one (which one is not important right now so I just go for the first entry in the list):
void RemoveEnemy ( )
{
if ( enemy.size ( ) > 0 )
enemy.erase ( enemy.begin ( ) );

Console::Print ( "Enemy removed - new enemy count: %d", enemy.size ( ) );
}

So, when I push-back a new Enemy into the list, I make sure to set its pointer to the correct model according to the type that the new enemy should be of. Like this, however, whenever I call RemoveEnemy ( ) the game crashes with this:
---------------------------
Microsoft Visual C++ Debug Library
---------------------------
Debug Assertion Failed!

Program: c:\Game\Game.exe
File: f:\dd\vctools\crt_bld\self_x86\crt\src\dbgdel.cpp
Line: 52

For information on how your program can cause an assertion
failure, see the Visual C++ documentation on asserts.

When I don't set the enemy's model-pointer to anything (leave it as NULL), and then don't try to draw it (access it), removing works fine. I'm assuming I'm doing something wrong with the boost::shared_ptrs, possibly when setting the smart pointer to point at the correct model structure? Also, is this approach valid? Does it make sense to do it all this way? Any help is appreciated!

Share on other sites
You're misusing shared_ptr here, making it point to a non-heap-allocated object and creating multiple shared_ptrs to the same object. On a more basic note, though, why are you using a smart pointer rather than a raw pointer in this instance? What do you intend for the smart pointer to handle for you?

Share on other sites
Quote:
 Original post by SneftelYou're misusing shared_ptr here, making it point to a non-heap-allocated object and creating multiple shared_ptrs to the same object.

Ah, didn't know you couldn't do that. I'm new to the boost::pointers.

Quote:
 Original post by SneftelOn a more basic note, though, why are you using a smart pointer rather than a raw pointer in this instance? What do you intend for the smart pointer to handle for you?

I was told to always use them, in this instance, though, using a normal raw pointer works flawlessly.

Thanks for the clear up, works fine now!

Share on other sites
Quote:
 Original post by d h kI was told to always use them, in this instance, though, using a normal raw pointer works flawlessly.
That doesn't answer my question. What does a shared_ptr do that a raw pointer doesn't? Hint: It's just one thing. (Answering this question will aid your understanding of smart pointers.)

Share on other sites
Free its own memory automatically when it's not needed anymore?

Share on other sites
Quote:
 Free its own memory automatically when it's not needed anymore?
Yup, pretty much.

Unless you're doing some unusual (such as constructing your shared pointers with a custom 'delete' function), shared_ptr will invoke delete on the held pointer when the reference count drops to zero.

So the next question is, what would you expect to happen when delete is invoked on a non-heap-allocated object, such as your global 'model' objects?

Create an account

Register a new account

• Partner Spotlight

• Forum Statistics

• Total Topics
627684
• Total Posts
2978627

• 9
• 14
• 12
• 10
• 12