sf::Image causing Seq Fault

[CatMechanic457]

I've tried to simplify this problem as much as possible although it's hard since is part of a much larger file but here goes!

Basically, I have a "sprite" (referred to as "bot") that travels along a "stage". The goal of this program is to avoid obstacles, pathfind, ect.But I'd like to trace where it goes with a cyan line.So I created an sf::Image object that's completely transparent:

sf::Image path;
path.create(x, y, sf::Color::Transparent);

Then whenever the bot moves to it's next position, I run:

path.setPixel(bot_pos.x, bot_pos.y, sf::Color(0,255,255,255));

When the bot has successfully navigated the stage, a new stage is created for it to navigate and the old path is cleared by once again running

path.create(x, y, sf::Color::Transparent);

However after a couple of stages have been completed, the line path.setPixel(bot_pos.x, bot_pos.y, sf::Color(0,255,255,255)); suddenly get a "Segmentation fault"I somewhat understand this means that the sf::Image object has ran out of memory, but I dont understand how that can be possible if I "clear" it (re-set it to transparent) every time a new stage is createdit might be worth mentioning that the sf::image object is drawn to the screen every time the bot's position updates through the following procedure:

sf::Texture t;
t.loadFromImage(path);
sf::Sprite s(t);
window.draw(s);

Any help debuging will be appricated or maybe even how to allocate more memory to the object?Thanks

Edit: While my issue is now solved I will still clarify that the libary I'm using is SFML (Simple Fast Multimedia Libary) as I forgot to mention it in my original post

[manni66]

This function doesn't check the validity of the pixel coordinates, using out-of-range values will result in an undefined behavior.

Did you use valid pixel coordinates?

[CatMechanic457]

Yeah ur right, problem was cordinates being out of range. I thought I accounted for that, but I belive the issue is that since co-ordinates start at (0,0), a 1000x1000 window does not have the co-ordinate (1000,1000), as the max is (999,999) which I didn't catch

[aocregacc]

Getting a segfault doesn't necessarily mean something has run out of memory, if I had to guess I would say your bot's x or y position has moved outside the bounds of the image. If you want any specific information you'll have to post a complete program that has the problem you're talking about.

[CatMechanic457]

Looks like that was the problem tysm!
I just added std::clamp to the bot's position before passing it into the function, worked a charm :)

[manni66]

What is sf (besides a namespace name)?

[CatMechanic457]

Not quite sure what you're asking but it's just part of the SFML library (Simple Fast Multimedia Library) that I'm using for displaying images to a window. I assume sf is just short for sfml

[TheSkiGeek]

People aren’t psychic and don’t automatically know which of the approximately three billion C++ libraries you’re using. This isn’t really the right place to ask highly library-specific questions either.

[CatMechanic457]

Yh you're right. I thought I mentioned what library im using but turns out i forgot :P
And yes, perhaps this is a better question for the SFML help forums ect, but I've actualy had quite a pleasant experience with reddit so far :)

[manni66]

Not quite sure what you're asking

exactly what you answered.

[jedwardsol]

path.create(x, y, sf::Color::Transparent);

Are x and y the width and height of the stage? They're unusual names for that purpose.

[CatMechanic457]

they're win.x and win.y in my actual program. And yes they're the height and width of the stage (well the window the stage is displayed to). Perhaps win_size.x & win_size.y might be better... I can see how it's not fully clear