At first glance, if you're blowing up on a simple get routine, it probably means you're using pointers but you messed up the pointer somewhere and it points to an invalid place. That means regardless of the method you call, it should explode because they're all pointing nowhere.
Either you're:
- adding invalid ones onto the STL list
- breaking the list somewhere
- Incorrectly keeping the number of elements on the list and when you delete some, you're going past the end.
- You're keeping a pointer to something that has been destroyed and then accessing it.
Actually, come to think of it, you shouldn't necessarily need to use pointers AND an STL list. If I recall correctly, you only need pointers AND STL lists when you use inheritance so you can tell whether you're talking to a base class or an inherited version at run-time.
Also, here:
#SelectExpand
1if((*iterEnemigos
)->GetestaVivo
())
2 {
3 if((*iterBalas
)->colision
(iterBalas, iterEnemigos
))
4 {
5 delete(*iterBalas
);
6 iterBalas
= balas.erase
(iterBalas
);
7 PROYECTILs_destruidas
++;
8
9 delete(*iterEnemigos
);
10 iterEnemigos
= enemigos.erase
(iterEnemigos
);
11 asteroides_destruidos
++;
12 nave->puntos
++;
13 al_play_sample(boom,
1,
0,
1, ALLEGRO_PLAYMODE_ONCE,
0);
14 if(!boom
)
15 cout
<< "NO BOOM!";
16 cout
<< "HE llegado";
17 }
18 }
19
20 else if((*iterBalas
)->fuera
(iterBalas, ALTURA_DISPLAY, ANCHURA_DISPLAY
))
21 {
22 delete (*iterBalas
);
23 iterBalas
= balas.erase
(iterBalas
);
24 PROYECTILs_destruidas
++;
25 }
It looks like you are deleting the object pointed to by iterEnemigos and iterBalas but immediately after that in the else if, you're dereferencing ("following") the pointer (that you destroyed) to nowhere, and then once at the nowhere you're trying to call methods on it which blow up.
That's not necessarily the GetX seg fault though.
]]>
