supertux2 crashed with SIGSEGV

Bug #183419 reported by DarkMageZ
64
This bug affects 8 people
Affects Status Importance Assigned to Milestone
supertux (Ubuntu)
Expired
Medium
Unassigned

Bug Description

Binary package hint: supertux

i think i told it to either quit or to not be full screen. then it crashed.

ProblemType: Crash
Architecture: i386
Date: Wed Jan 16 15:07:40 2008
DistroRelease: Ubuntu 8.04
ExecutablePath: /usr/games/supertux2
NonfreeKernelModules: cdrom
Package: supertux 0.3.1d-0ubuntu1
PackageArchitecture: i386
ProcCmdline: supertux2
ProcCwd: /home/richard
ProcEnviron:
 PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games
 LANG=C
 SHELL=/bin/bash
Signal: 11
SourcePackage: supertux
StacktraceTop:
 ?? ()
 ?? ()
 ?? ()
 ?? ()
 ?? ()
Title: supertux2 crashed with SIGSEGV
Uname: Linux DarkMageZ 2.6.24-3-generic #1 SMP Thu Jan 3 23:30:29 UTC 2008 i686 GNU/Linux
UserGroups: adm admin audio cdrom dialout dip floppy lpadmin netdev plugdev powerdev scanner video
SegvAnalysis:
 Segfault happened at: 0x80f324e <_ZNSt8ios_base4InitD1Ev@plt+674166>: mov 0x20(%eax),%edx
 PC (0x080f324e) ok
 source "0x20(%eax)" (0x00000020) not located in a known VMA region (needed readable region)!
 destination "%edx" ok
SegvReason: reading NULL VMA

Tags: apport-crash
Revision history for this message
DarkMageZ (darkmagez) wrote :
Revision history for this message
Apport retracing service (apport) wrote : Symbolic stack trace

StacktraceTop:Menu::is_toggled (this=0x0, id=0) at src/gui/menu.cpp:758
OptionsMenu::menu_action (this=0x8e61b80, item=0x8f6b590)
Menu::update (this=0x8e61b80) at src/gui/menu.cpp:412
TitleScreen::update (this=0x879c240,
MainLoop::update_gamelogic (this=0x8652998,

Revision history for this message
Apport retracing service (apport) wrote : Symbolic threaded stack trace
Revision history for this message
Apport retracing service (apport) wrote : Stack trace with source code
Changed in supertux:
importance: Undecided → Medium
Revision history for this message
John Dong (jdong) wrote :

I tried both actions at least 10 times on my two systems each and could not reproduce a crash. Do you have any other suggestions for reproducing it?

Changed in supertux:
status: New → Incomplete
Revision history for this message
DarkMageZ (darkmagez) wrote :

not really. but this is why we have stacktraces.

stacktraces can be used by the developers to figure out what went wrong.

stacktraces are used to find out the cause of those once in a million crashers.

Changed in supertux:
status: Incomplete → New
Revision history for this message
John Dong (jdong) wrote :

Indeed it is. Thanks to the stacktrace, I can see where the pointer went null but have no idea how that code path could've been taken. It'd be kinda painful to check every foo->bar reference for nullness, or even what to do when that happens.

Maybe this should be forwarded upstream, since it's a development version and they'd be more interested about this crasher?

Judging from the stacktrace, it seems like you were toggling the fullsceen option which caused this.

Revision history for this message
old_toby (simon-hornweb) wrote :

Exactly. It happened here too when I told it not be fullscreen anymore.

Changed in supertux:
status: New → Confirmed
Revision history for this message
Don Zavitz (dzavitz) wrote :

i was fullscreen, trying to make it go windowed and it crashed...

next time it worked goin from FS to windowed..

Kees Cook (kees)
description: updated
Revision history for this message
Don Forigua (ingforigua) wrote :

I use the nvidia-glx-185 and it crash when i lose a level, i have graphic aceleration.

Revision history for this message
Don Forigua (ingforigua) wrote :

Sorry i use ubuntu karmic koala beta

Revision history for this message
Thomas Hotz (thotz-deactivatedaccount) wrote :

Your Ubuntu version is EOL on the desktop. Can you reproduce this error with a supported Ubuntu version? Thank you!

Changed in supertux (Ubuntu):
status: Confirmed → Incomplete
Revision history for this message
Launchpad Janitor (janitor) wrote :

[Expired for supertux (Ubuntu) because there has been no activity for 60 days.]

Changed in supertux (Ubuntu):
status: Incomplete → Expired
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.