A simple stack trace or a core dump where the application crashes is
pretty vital to real debugging. Try to learn to do that as soon as
possible. I haven’t developed on MSWindows for a decade so I can’t
tell you how to get it, unfortunately.
What exactly is “compatibility mode?”
You’ve been very helpful listing system (OS) software you’ve tried
running on, but have you been observing what kind of CPU architecture
you’re running on? Could “compatibility mode” possibly be the
difference between supporting the instruction set your build is
You should also always make sure you know exactly what you’re linking
to. You might find that on systems that work, you’re linking to a
specific build or version of a DSO (DLL) and different ones when it
doesn’t work. On *NIX the “ldd” command will behave as the dynamic
linker and determine what DSOs your app will link to when run with the
same settings you run ldd from. On MSWindows you have Dependency
Walker, a must-have tool for MSWindows developers if things are the
way they were ten years ago!
Good luck solving your problem! A stack trace would be very helpful
for others trying to determine the problem.
Also it’s really important that you try to reproduce this problem with
an SDL test application. I would recommend one but I don’t know which
one might use SDL_image. Perhaps there is an SDL_image test app that I
never really noticed that you could use. In any case, you should
quickly determine whether the problem lies in your app, your build
tools, or in SDL or SDL_image!On Thu, Aug 26, 2010 at 5:07 PM, feodor wrote:
I’m attempting to make a game using the SDL library, however I’m having some
trouble getting my application to run - both on my own computer and on
others.’ What’s weird about it, is that my game runs fine when using the
debugger of Microsoft Visual C++ 2010, the problem appears when trying to
run the executable from outside the IDE.
On my Windows 7 machine the window greys out, another window pops up saying
that ‘App.exe has stopped working’, and that ‘Windows is checking for a
solution to the problem.’ If I run the application with a compatibility mode
of anything from Windows NT 4.0 (SP 5) and onwards the program runs fine.
On my Windows XP machine the application wont open; it says something along
the lines of ‘App.exe has encountered a problem and needs to close. We are
sorry for the inconvenience.’
The only thing in my project configuration that differs from normal (ie.
setting library and include folders, setting additional dependencies and
changing subsystem to windows), is that I’ve set Runtime Library to
’Multi-Threaded /MT’, instead of ‘Multi-Threaded DLL /MD’ - to prevent
others from having to install the Visual C++ Redistributable to run the
application (I did recompile SDL so it works with this).
Has anyone else experienced something similar – or do you have any idea
what this could be happening? If you want me to post some source code, I
will, but everything compiles fine and runs fine under some circumstances,
so I’m unsure where in the code I could have a problem, hopefully I can get
a hint as to where to look.
I did try to search both here on this forum and google, but I didn’t find a
solution to my problem - hope someone here can help me.
SDL mailing list
SDL at lists.libsdl.org