[apport] armagetron.real crashed with SIGSEGV

Bug #117351 reported by PatrynXX
10
Affects Status Importance Assigned to Milestone
armagetronad (Ubuntu)
Confirmed
Medium
Unassigned

Bug Description

Binary package hint: armagetron

Started up kubuntu and it crashed. Subject header doesn't match any of the above.

ProblemType: Crash
Architecture: i386
Date: Sun May 27 07:08:27 2007
DistroRelease: Ubuntu 7.04
ExecutablePath: /usr/games/armagetron.real
Package: armagetron 0.2.7.0-1.1ubuntu2
PackageArchitecture: i386
ProcCmdline: /usr/games/armagetron.real --datadir /usr/share/games/armagetron --configdir /etc/armagetron --userconfigdir /home/lee/.armagetron --vardir /home/lee/.armagetron/var
ProcCwd: /home/lee
ProcEnviron:
 PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games
 LANG=en_US.UTF-8
 SHELL=/bin/bash
Signal: 11
SourcePackage: armagetron
Stacktrace:
 #0 0xb7bbaa16 in ?? () from /lib/tls/i686/cmov/libc.so.6
 #1 0x00000000 in ?? ()
StacktraceTop:
 ?? () from /lib/tls/i686/cmov/libc.so.6
 ?? ()
ThreadStacktrace:
 .
 Thread 1 (process 6477):
 #0 0xb7bbaa16 in ?? () from /lib/tls/i686/cmov/libc.so.6
 #1 0x00000000 in ?? ()
Uname: Linux lee-desktop 2.6.20-15-generic #2 SMP Sun Apr 15 07:36:31 UTC 2007 i686 GNU/Linux
UserGroups: adm admin audio cdrom dialout dip floppy lpadmin netdev plugdev powerdev scanner video

Revision history for this message
PatrynXX (sage-patrynxx) wrote :
Revision history for this message
Apport retracing service (apport) wrote : Symbolic stack trace

StacktraceTop:malloc_consolidate () from /lib/tls/i686/cmov/libc.so.6
_int_malloc () from /lib/tls/i686/cmov/libc.so.6
malloc () from /lib/tls/i686/cmov/libc.so.6
ReadInFile (filename=<value optimized out>) at ../../src/Xrm.c:1604
XrmGetFileDatabase (filename=0xb737180c "/usr/share/X11/XErrorDB") at ../../src/Xrm.c:1669

Revision history for this message
Apport retracing service (apport) wrote : Symbolic threaded stack trace
Changed in armagetronad:
importance: Undecided → Medium
status: Unconfirmed → Confirmed
Revision history for this message
Manuel Moos (z-man) wrote :

Does this still happen? If yes, could I see a console log? Just start the game on a X terminal of any kind via

armagetronad

Thing is, the callstack basically says it's an exit crash, not a startup crash. Something else must have gone wrong during startup that caused the immediate exit, for example a failure to initialize GLX. Those don't usually cause crashes, though.

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.