Segfault on launch

Issue #9 closed
Douglas created an issue

Cannot lauch the game. It sigsegvs on "Loading..." stage:

{{{ #!bash

... Identified level: finalscene2.lev furthest save path: /home/username/.Puzzle Moppet/puzzlegame.save.furthest Level::Level: ../projects/Puzzle/levels/levels/titlescreen.lev

Program received signal SIGSEGV, Segmentation fault. 0x00000000 in ?? () (gdb) bt #0 0x00000000 in ?? () }}}

Comments (7)

  1. Douglas reporter

    When I've changed the top level CMakeLists.txt (as was suggested by Garnet Games) into

    #set(CMAKE_CXX_FLAGS "-Wall")
    set(CMAKE_CXX_FLAGS_DEBUG "-g") # for line numbers
    #set(CMAKE_CXX_FLAGS_RELEASE "")
    
    set(CMAKE_BUILD_TYPE Debug)
    #set(CMAKE_BUILD_TYPE Release)
    

    I got:

    ...
    Identified level: finalscene1.lev
    Identified level: finalscene2.lev
    furthest save path: /home/username/.Puzzle Moppet/puzzlegame.save.furthest
    Level::Level: ../projects/Puzzle/levels/levels/titlescreen.lev
    
    Program received signal SIGSEGV, Segmentation fault.
    0x10210cc0 in DynamicBody::DynamicBody (this=0x3ffacee9,
    world=0xf37bebd5, __in_chrg=<optimized out>, __vtt_parm=<optimized
    out>)
        at /home/username/Development/PuzzleMoppet/PuzzleMoppetSource/Litha
    Engine/source/Physics/DynamicBody.cpp:43
    43              dBodySetMass(body, &dmass);
    (gdb) bt
    #0  0x10210cc0 in DynamicBody::DynamicBody (this=0x3ffacee9,
    world=0xf37bebd5, __in_chrg=<optimized out>, __vtt_parm=<optimized
    out>)
        at /home/username/Development/PuzzleMoppet/PuzzleMoppetSource/Litha
    Engine/source/Physics/DynamicBody.cpp:43
    #1  0x00000000 in ?? ()
    (gdb)
    
  2. Douglas reporter

    Did it. Got:

    $ valgrind ./Litha\ Engine/bin/PuzzleGame_FullVersion 
    ==17381== Memcheck, a memory error detector
    ==17381== Copyright (C) 2002-2011, and GNU GPL'd, by Julian Seward et al.
    ==17381== Using Valgrind-3.7.0 and LibVEX; rerun with -h for copyright info
    ==17381== Command: ./Litha\ Engine/bin/PuzzleGame_FullVersion
    ==17381== 
    Litha Game Engine
    Arg: ./Litha Engine/bin/PuzzleGame_FullVersion
    Actual executable path: /home/username/Development/PuzzleMoppet/PuzzleMoppetSource/Litha Engine/bin/PuzzleGame_FullVersion
    Settings path: /home/username/.Puzzle Moppet/Puzzle Moppet.ini
    Logging to /home/username/Development/PuzzleMoppet/PuzzleMoppetSource/Litha Engine/bin/Puzzle Moppet.log
    Also logging to /var/log/Puzzle Moppet.log
    Original starting path: /home/username/Development/PuzzleMoppet/PuzzleMoppetSource
    Querying current desktop resolution...
    *** WARNING at Engine.cpp:172:Engine: Failed to create Irrlicht NULL Device.
    Changing directory to /home/username/Development/PuzzleMoppet/PuzzleMoppetSource/Litha Engine/bin
    Current directory is now /home/username/Development/PuzzleMoppet/PuzzleMoppetSource/Litha Engine/bin
    Fullscreen: 0
    VSync: 1
    Max render FPS: 60.0
    *** FATAL ERROR at Engine.cpp:222:Engine: Could not create Irrlicht Device.
    ==17381== 
    ==17381== HEAP SUMMARY:
    ==17381==     in use at exit: 7,230 bytes in 245 blocks
    ==17381==   total heap usage: 1,593 allocs, 1,348 frees, 64,750 bytes allocated
    ==17381== 
    ==17381== LEAK SUMMARY:
    ==17381==    definitely lost: 0 bytes in 0 blocks
    ==17381==    indirectly lost: 0 bytes in 0 blocks
    ==17381==      possibly lost: 0 bytes in 0 blocks
    ==17381==    still reachable: 7,230 bytes in 245 blocks
    ==17381==         suppressed: 0 bytes in 0 blocks
    ==17381== Rerun with --leak-check=full to see details of leaked memory
    ==17381== 
    ==17381== For counts of detected and suppressed errors, rerun with: -v
    ==17381== ERROR SUMMARY: 0 errors from 0 contexts (suppressed: 5 from 3)
    Aborted
    
  3. karjonas

    Well, it says that it could not create an irrlicht device for some reason. I noticed that you are running an old binary, PuzzleGame_Fullversion is called puzzlegame now, so all I can suggest at this point is to pull down the latest version and recompile.

  4. Log in to comment