Welcome, Guest. Please login or register. Did you miss your activation email?

Show Posts

This section allows you to view all posts made by this member. Note that you can only see posts made in areas you currently have access to.


Topics - Neo1

Pages: [1]
1
General discussions / Works fine on one machine, crashes on the other?
« on: October 28, 2011, 05:42:06 pm »
So i've just finished a tiny hobby project that generates a random perfect maze using a randomized DFS. I coded it all on my laptop (Running Windows 7) using Code::Blocks 10.05 and MinGW with GCC 4.5.2, it's not quite finished and polished yet, but it works and runs. I use the dynamic libraries and i link against:

-lsfml-graphics-d
-lsfml-window-d
-lsfml-system-d

I define SFML_DYNAMIC and the proper DLLs are where they belong, so far so good.

So since the program runs quite slowly (I'm doing some stupid conversions and copies of some semi-large vectors in my main loop, as i said, not quite finished yet) i wanted to try it out on my significantly faster desktop.

First of i couldn't compile the code since the GCC version didn't have the proper dll (Something with exceptions and something called Dwarf2 i believe), so i fixed this error by just uninstalling C::B and MinGW, and then installing the newest version of MinGW seperately from C::B. I then set up the new project exactly as above, it compiles like a dream, but when i run it i just get an empty console window. No renderwindow, no nothing. If i set a breakpoint just at the start of main and run it through the debugger, GDB just crashes before it even reaches main.

This machine also runs Windows 7, both MinGW and C::B is the exact same version as on my laptop. I even tried copying the executable from my laptop to the desktop, and it still just gives me an empty console window, although the exact same executable works like a dream on the laptop, with a pretty much identical setup.

What is going on here? I can post the code if need be, it's not that long, but somehow i don't think this has anything to do with the code itself.

Pages: [1]