Blue screen after compiling

  • New-IdeasForYou
    7th Jun 2013 Member 0 Permalink

    I compiled powder toy, but it just goes blue: 

     

    error

     

    output in the console: 

     

    First-chance exception at 0x001ded70 in tpt.exe: 0xC0000005: Access violation reading location 0x000004db.
    The thread 'Win32 Thread' (0x1064) has exited with code -1 (0xffffffff).
    The thread 'Win32 Thread' (0xe38) has exited with code -1 (0xffffffff).
    The program '[2400] tpt.exe: Native' has exited with code -1 (0xffffffff).

  • cyberdragon
    7th Jun 2013 Member 0 Permalink

    compiler error, it must have attempted to overwrite something it shouldn't, like active memory.

     

    EDIT: I mean, the game tried to overwrite something because it was compiled wrong. Check preprocessor,   check for SSE2, and dependancies.

  • boxmein
    8th Jun 2013 Former Staff 1 Permalink
    @cyberdragon (View Post)
    duh

    @New-IdeasForYou (View Post)
    I got the same thing today, both with release and debug. I am certain my builds are okay, yet it seems the latest source itself is unstable. Let's wait.
  • jacob1
    8th Jun 2013 Developer 0 Permalink
    Odd ... since i'm compiling with visual studio too and don't get any problem.

    Try going into PowderToySDL.cpp and finding these lines:

    #ifndef DEBUG
    //Get ready to catch any dodgy errors
    signal(SIGSEGV, SigHandler);
    signal(SIGFPE, SigHandler);
    signal(SIGILL, SigHandler);
    signal(SIGABRT, SigHandler);
    #endif

    And commenting them out or something temporarily, then it will let you debug again and see where the real error is. I need to fix compiling in debug mode with visual studio having these bluescreens ... which I already know how to do
  • mniip
    8th Jun 2013 Developer 0 Permalink
    Access violation reading location 0x000004db.

    either some fuck-up resulting in a jump into non-code,
    or some fuck-up wiping DS register
  • New-IdeasForYou
    8th Jun 2013 Member 0 Permalink

    @jacob1 (View Post)

     Im not debugging, Im actually releasing, like the tutorial said. 

    But after commenting them, i got a VS violation warning: 

    Unhandled exception at 0x000ded70 in tpt.exe: 0xC0000005: Access violation reading location 0x000004db.

     

    But it must be my own flaw. I will download the source again. Anyways, thnks for the help, if i keep getting erros i let you know :)

     

    Edit: ok, still getting the same error. -.-

  • jacob1
    8th Jun 2013 Developer 0 Permalink
    @New-IdeasForYou (View Post)
    yeah, but when you run something from visual studio it's probably also loading the debugger. If you aren't, you will probably want to debug the crash, so I would go comment out those lines and see if you can tell me what line it crashes on.
  • New-IdeasForYou
    8th Jun 2013 Member 0 Permalink

    @jacob1 (View Post)

     Im not really good using debug, but it shows a lot of errors, (weird, when compiling for released it showed no errors... ) like: 

     

    src\pim\Machine.cpp(6): fatal error C1083: Cannot open include file: 'simulation/Simulation.h': No such file or directory

     

    rc\pim\Generator.cpp(4): fatal error C1083: Cannot open include file: 'Format.h': No such file or directory

     

    1>src\Misc.cpp(5): fatal error C1083: Cannot open include file: 'regex.h': No such file or directory

     

    desktop\tpt source\src\gui\save\LocalSaveActivity.h(3): fatal error C1083: Cannot open include file: 'Activity.h': No such file or director

     

    desktop\tpt source\src\cat\TPTSTypes.h(6): fatal error C1083: Cannot open include file: 'gui/interface/Point.h': No such file or directory

     

    And much more of these, like, a hundred. And its weird because i checked and they are all in the directory... wth is that? 

  • jacob1
    8th Jun 2013 Developer 0 Permalink
    In the compiling guide, you probably missed the step where you had to add the include directories. You have to add src/ as one of them.

    Edit: actually it's because when following the guide, you only followed the steps while changing the release mode settings. Which is really annoying that visual studio does that, I used to do that all the time. You might have to follow parts of the guide again to see. Or maybe i'll figure out the error on my own somehow ...
  • boxmein
    8th Jun 2013 Former Staff 0 Permalink
    > 0xC0000005
    Every time I compiled it's this line.
    This demonic satanic line.
    0xC0000005.
    Just look at it.
    Look at the menacing x and how all the zeros just STARE at you
    It's no wonder the line causes this.