#1 2014-07-31 14:23:05

restcoser
Member

[Solved]Crash after a few minutes of CTF, segmention fault

After playing a bit of CTF today my client crashed after roughly 7 (?) minutes of play. (version r1797, pretty sure I had this crash already on an earlier revision though)

I was able to reproduce the issue by just playing any ctf map (tested on different maps). (I was testing with two bots, I'm not sure if that influences the crash)

However, the data I'm getting out of backtracing with gdb seems not very helpful (maybe I did the backtrace wrong, I tried following the instructions on https://wiki.debian.org/HowToGetABacktrace)

The crash happened first  by just the window closing itself with the console output "Segmention fault", when running it via gdb instead of closing directly, it froze and my Window Manager/OS offered me to kill it/close it (which i did)
The output I received:

restcoser@restcoser-LM16 ~/Programs/svn/tesseract $ gdb ./bin_unix/native_client 
GNU gdb (GDB) 7.6.1-ubuntu
Copyright (C) 2013 Free Software Foundation, Inc.
License GPLv3+: GNU GPL version 3 or later <http://gnu.org/licenses/gpl.html>
This is free software: you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law.  Type "show copying"
and "show warranty" for details.
This GDB was configured as "x86_64-linux-gnu".
For bug reporting instructions, please see:
<http://www.gnu.org/software/gdb/bugs/>...
Reading symbols from /home/restcoser/Programs/svn/tesseract/bin_unix/native_client...(no debugging symbols found)...done.
(gdb) run -u/home/restcoser/.tesseract
Starting program: /home/restcoser/Programs/svn/tesseract/./bin_unix/native_client -u/home/restcoser/.tesseract
[Thread debugging using libthread_db enabled]
Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".
Using home directory: /home/restcoser/.tesseract/
init: sdl
[New Thread 0x7fffed520700 (LWP 12482)]
[New Thread 0x7fffe861e700 (LWP 12484)]
[Thread 0x7fffe861e700 (LWP 12484) exited]
init: net
init: game
init: video
init: gl
Renderer: GeForce GT 630/PCIe/SSE2 (NVIDIA Corporation)
Driver: 4.0.0 NVIDIA 319.32
GLSL: 4.00 NVIDIA via Cg compiler
Rendering using the OpenGL GLSL shader path.
init: console
init: world
init: sound
[New Thread 0x7fffe861e700 (LWP 12485)]
init: cfg
init: render
init: mainloop
[New Thread 0x7fffeac1b700 (LWP 12493)]
[New Thread 0x7fffea41a700 (LWP 12494)]
attempting to connect to 158.129.0.38:42000
connected to server
read map media/map/test_ctf.ogz (0.0 seconds)
game mode is pCTF
Pulse Rifle Capture The Flag:
Capture the enemy flag and bring it back to your flag to score points for your team.

<snip generic ctf action output>

rojo's flag reset
you stole rojo's flag
you suicided!
you dropped rojo's flag
rojo's flag reset

Program received signal SIGSEGV, Segmentation fault.
0x000000000067da04 in ?? ()
(gdb) bt
#0  0x000000000067da04 in ?? ()
#1  0x000000000065341b in ?? ()
Cannot access memory at address 0x7fffffffdd68
(gdb) bt full
#0  0x000000000067da04 in ?? ()
No symbol table info available.
#1  0x000000000065341b in ?? ()
No symbol table info available.
(gdb) 

Required System Data:

System: Linux Mint 16 Cinnamon Edition

Renderer: GeForce GT 630/PCIe/SSE2 (NVIDIA Corporation)
Driver: 4.0.0 NVIDIA 319.32
GLSL: 4.00 NVIDIA via Cg compiler
Rendering using the OpenGL GLSL shader path.

Tesseract version: r1797


Let me know if i can provide in any way more helpful output :/

Last edited by restcoser (2014-08-01 06:14:45)

Offline

#2 2014-07-31 18:15:27

eihrul
Administrator

Re: [Solved]Crash after a few minutes of CTF, segmention fault

You need to compile with make CXXFLAGS=-g3

Otherwise the backtrace tells me nothing.

Offline

#3 2014-08-01 06:14:19

restcoser
Member

Re: [Solved]Crash after a few minutes of CTF, segmention fault

Supplement: The bug was chased down/debugged and solved on IRC yesterday (or today, depending on timezone :P) and should be fixed in r1799 and up.

Offline

Board footer