Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

pointer being freed was not allocated #510

Closed
Sosukodo opened this issue Dec 18, 2013 · 7 comments
Closed

pointer being freed was not allocated #510

Sosukodo opened this issue Dec 18, 2013 · 7 comments

Comments

@Sosukodo
Copy link

The following code is enough to reproduce the problem.
SFML 2.1 stable

#include <SFML/Graphics.hpp>

int main()
{
    //sf::RenderWindow window(sf::VideoMode(320, 240, 32), "Test");

    sf::Text t_score;

}

Compiling on Mac OSX 10.6.8:

g++ test.cpp -o test -lsfml-graphics

./test

test(1075) malloc: *** error for object 0xee18c: pointer being freed was not allocated
*** set a breakpoint in malloc_error_break to debug

@MarioLiebisch
Copy link
Member

Did you try this with the latest version? Doesn't happen for me.

@mjbshaw
Copy link

mjbshaw commented Dec 18, 2013

Perhaps #5?

@Sosukodo
Copy link
Author

Yes, it still happens after building and installing the latest.

@mjbshaw: Yes. It happens with the #5 example, too!

@Bromeon
Copy link
Member

Bromeon commented Mar 26, 2014

Can anybody else reproduce this issue? Sounds very specific, I can't imagine all the OS X users having this bug, when already such a simple code leads to the problem.

Are you sure there is no configuration problem on your side?

@mjbshaw
Copy link

mjbshaw commented Mar 26, 2014

Can anybody else reproduce this issue? Sounds very specific, I can't imagine all the OS X users having this bug, when already such a simple code leads to the problem.

This is just #5. He's using OS X 10.6.8 and GCC, and has the same issues as the simpler code in #5. It's not a problem since Xcode 4.2 because Xcode 4.2 removed GCC and libstdc++. But if someone hasn't upgraded to Xcode 4.2 (and they're using GCC with libstdc++) then it would still be a problem for them.

@Bromeon
Copy link
Member

Bromeon commented Mar 26, 2014

Okay, thanks for clarifying that this is a duplicate.

@mjbshaw
Copy link

mjbshaw commented Mar 26, 2014

Okay, thanks for clarifying that this is a duplicate.

Cheers :D

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

5 participants