[SOLVED] Crash when draw() is used

[Antonio9227]

Hello, I am a object oriented programming newbie and I've encountered a weird problem while trying to make a level class. My application crashes every time I try to draw a level object, here is the code I'm using:

virtual void draw(sf::RenderTarget &target,sf::RenderStates states) const
{
    states.transform *=getTransform();
    states.texture = m_texture;
    target.draw(m_vertices,states); //Crashes here
}
 

During debug I receive an SIGSEGV segmentation fault signal when that specific line is executed. If I disable it the program runs as expected. m_vertices is a sf::VertexArray and m_texture is a sf::Texture pointer.
Also it doesn't matter if I constructed a mesh inside the vertex array or not, it still crashes. I've used the exact same piece of code for another class and it works just fine.

I really don't know what the problem could be and some help would be appreciated. 
Thanks in advance, regards Antonio.

[eXpl0it3r]

Run it through the debugger, check the call stack and make sure all your used objects are valid.

[Hapax]

I fancy a guess that it's the m_texture pointer that's invalid.

I'm allowed to guess, right?

[Antonio9227]

I had some spare time today so I read my code. I found my mistake and it had nothing to do with SFML. I had a function to load the level and that function did not worked properly. At a point my function was accessing items from an array (that was holding my tile information), my index was out of bound and I think it somehow managed to modify some bytes of the place where my vertex array was stored in the memory. Is this even possible?
Anyways, this is the only explanation I could come up with, thanks anyways for trying to help.

[eXpl0it3r]

my index was out of bound and I think it somehow managed to modify some bytes of the place where my vertex array was stored in the memory. Is this even possible?

To some degree, yes. Accessing the element beyond the last index of an array or vector is by the standard legal, but modifying that position will cause undefined behavior and it you're lucky you'll corrupt the stack and application will crash. If you're unlucky it will keep running and you never notice that you're doing something wrong.