#64 rev 3070 craches when switching to external view

crashes (68)

I compiled rev 3070 on a 64 bit Ubuntu Jaunty (9.04).
The menu show up and the game starts, but after a couple of seconds, when I try to switch to an external view (deck F4, or free view F10) the game crashes.

Here is the trace:
~/dangerdeep/svn$ build/linux/dangerdeep
Vendor: NVIDIA Corporation
Render: GeForce 6200/PCI/SSE2
Version: 2.1.2 NVIDIA 180.44
GLSL: 1.20 NVIDIA via Cg compiler
[Good] :-) OpenGL Version: 2.1.x
[Good] :-) Found 4 Texture Units and 16 Image Texture Units
[Good] :-) Support for vertex buffer objects
[Good] :-) Support for framebuffer objects
[Good] :-) Support for non power of two textures
[Good] :-) Support for fragment shaders
[Good] :-) Support for vertex shaders
[Good] :-) Support for shader objects
[Good] :-) Support for texture compression
[Good] :-) Support for 16bit floats
SIGSEGV caught!
Stack trace: (16 frames)
0x427e19 in build/linux/dangerdeep at faulthandler.h:369
0x415024 in build/linux/dangerdeep at stdio2.h:99
0x7f67108fa040 in /lib/libc.so.6 at ??:0
0x7f670fc28a44 in /usr/lib/libGLcore.so.1 at ??:0
0x7f670fc29c59 in /usr/lib/libGLcore.so.1 at ??:0
0x7f670fbd2905 in /usr/lib/libGLcore.so.1 at ??:0
0x7f670f8b2dae in /usr/lib/libGLcore.so.1 at ??:0
0x7f670f910625 in /usr/lib/libGLcore.so.1 at ??:0
0x7f670fcdf656 in /usr/lib/libGLcore.so.1 at ??:0
0x7f670f8ad73b in /usr/lib/libGLcore.so.1 at ??:0
0x7f670f8ad91e in /usr/lib/libGLcore.so.1 at ??:0
0x571a9c in build/linux/dangerdeep at framebufferobject.cpp:132
0x538135 in build/linux/dangerdeep at water.cpp:1362
0x456356 in build/linux/dangerdeep at freeview_display.cpp:448
0x454de3 in build/linux/dangerdeep at freeview_display.cpp:169
0x52fed5 in build/linux/dangerdeep at user_interface.cpp:374
Aborting program.


  • Gunee

    Gunee - 2009-10-20

    The problem not only occurs when switching to an external view, but also to the periscope view

  • Matthias Bady

    Matthias Bady - 2009-10-26

    Hi Gunee,

    please start dangerdeep with --debug and try to switch to an external view again. The --debug switch gives you a much more verbose output. Please attach the ouput.


  • Matthias Bady

    Matthias Bady - 2009-10-26
    • assigned_to: nobody --> mbady
  • Nobody/Anonymous

    I ran dangerdeep with the debug flag, and when it crashed, I got the same trace, with no additional info abou the problem.

    I also ran the executalbe in gdb, but at the moment of the crash, the sceen doesn't give the hand back to gdb, and therefore, the screen freezes to black. When I kill gdb, I get no additional info.

    But I could notice that the bug seems to be happening only when I run dangerdeep with a 1280x1024 screen resolution. With a 1024x768 rez, it worked fine.

  • Matthias Bady

    Matthias Bady - 2009-11-04

    Related to the graphic driver.
    Driver is proprietary so we can't trace the bug. Furthermore it's an old driver.

  • Matthias Bady

    Matthias Bady - 2009-11-04
    • status: open --> closed-wont-fix

Get latest updates about Open Source Projects, Conferences and News.

Sign up for the SourceForge newsletter:

No, thanks