Access violation with sf::Texture, only in Debug

[kennyrkun]

Creating a simple server-client demo, and the Client will not run when compiled in Debug mode via Visual Studio.

The offending code:

#include <SFML/Graphics.hpp>

sf::Texture tex;

int main()
{
}
 

Run in a debugger, the program crashes immediately a points to the declaration of tex as the culprit.
 

Exception thrown at 0x77E90E72 (ntdll.dll) in Client.exe: 0xC0000005: Access violation writing location 0x00000004.

This only happens when compiled in debug mode. If I remove the declaration of tex, it compiles and runs with no issues, so I don't believe I have any linker mismatches, but just in case, here's the call stack Visual Studio reports:



I have no idea what's causing this so called access violation. It's only now that it's causing this issue, where yesterday, and a month ago, all was well. The accompanying server project has a few variables in the global scope of main.cpp and it compiles and runs in both debug and release with no issues.

save me.

[Laurent]

It's generally a good idea to avoid declaring SFML resource classes at global scope, as they sometimes need to make calls that rely on other globals (like here) that may not be initialized yet.

Regarding this specific one, I may be wrong but I think it might be "fixed" in the latest sources.

[netrunner]

Creating a simple server-client demo, and the Client will not run when compiled in Debug mode via Visual Studio.

The offending code:

#include <SFML/Graphics.hpp>

sf::Texture tex;

int main()
{
}
 

Run in a debugger, the program crashes immediately a points to the declaration of tex as the culprit.
 

Exception thrown at 0x77E90E72 (ntdll.dll) in Client.exe: 0xC0000005: Access violation writing location 0x00000004.

This only happens when compiled in debug mode. If I remove the declaration of tex, it compiles and runs with no issues, so I don't believe I have any linker mismatches, but just in case, here's the call stack Visual Studio reports:



I have no idea what's causing this so called access violation. It's only now that it's causing this issue, where yesterday, and a month ago, all was well. The accompanying server project has a few variables in the global scope of main.cpp and it compiles and runs in both debug and release with no issues.

save me.

Hey, Kenny!

I'm having this issue too, and I'm not having a particularly easy time fixing it. It's been a few months since you've posted this thread (sorry for the necro), would you happen to remember what the problem was/how you went about fixing it?

Thanks in advance.