Now I will preface by saying this could be a VS issue or something with my PC although I'd hope my processor has the power to handle it but I've been through all the typical steps so wanted to see if anyone has had this issue with SFML before.
I have an SFML 3.0 project and I built the libs myself using cmake. I couldn't get it to create the dynamic libraries so have linked it statically but am not sure that's even the issue.
It all compiles and runs fine but I wanted to check to make sure some texture swapping was working properly and every time I tried to inspect the sf::texture (as either a local, member variable, ptr etc.) it would cause Visual Studio to say it was busy and then usually abort the execution complaining that "The debugger's worker process (msvsmon.exe) unexpectedly exited"
As a sanity check I made a quick new empty project and tested it with 2.6 dynamically linked, 2.6 statically linked (both using the pre-built download from SFML resources), and 3.0 that I built myself. With this empty project that just creates a texture and renders an empty window I could inspect the 2.6 texture but not on 3.0; same issue as before.
Could this be an issue with how I've built 3.0 myself or is this some other known issue people have come across before with 3.0? It's not like I can't work at all like this but it's very odd and I've never seen something like this before.
Cheers
