wesnoth crashed with SIGSEGV in malloc()

Bug #295569 reported by Cyril
8
Affects Status Importance Assigned to Milestone
wesnoth (Ubuntu)
Invalid
Medium
Unassigned

Bug Description

Binary package hint: wesnoth

hello,
In multiplayer, LAN, i chosen a game. When i clicked for validate, the game frozen.
Regards

ProblemType: Crash
Architecture: i386
Date: Sat Nov 8 15:07:20 2008
DistroRelease: Ubuntu 8.04
ExecutablePath: /usr/games/wesnoth
NonfreeKernelModules: nvidia
Package: wesnoth 1:1.4.4-2~hardy1
PackageArchitecture: i386
ProcCmdline: wesnoth
ProcEnviron:
 PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games
 LANG=fr_FR.UTF-8
 SHELL=/bin/bash
Signal: 11
SourcePackage: wesnoth
StacktraceTop:
 ?? () from /lib/tls/i686/cmov/libc.so.6
 ?? () from /lib/tls/i686/cmov/libc.so.6
 malloc () from /lib/tls/i686/cmov/libc.so.6
 operator new () from /usr/lib/libstdc++.so.6
 std::string::_Rep::_S_create () from /usr/lib/libstdc++.so.6
Title: wesnoth crashed with SIGSEGV in malloc()
Uname: Linux 2.6.24-21-generic i686
UserGroups: adm admin audio cdrom dialout dip floppy fuse lpadmin plugdev sambashare scanner vboxusers video

Revision history for this message
Cyril (i3s7) wrote :
Revision history for this message
Apport retracing service (apport) wrote : Symbolic stack trace

StacktraceTop:?? ()
?? ()
?? ()
?? ()
?? ()

Revision history for this message
Pedro Villavicencio (pedro) wrote : Missing Backtrace

Thanks for your bug report. Please try to obtain a backtrace http://wiki.ubuntu.com/DebuggingProgramCrash and attach the file to the bug report. This will greatly help us in tracking down your problem.

Changed in wesnoth:
importance: Undecided → Medium
status: New → Incomplete
Revision history for this message
Cyril (i3s7) wrote :

hello,
the game doesn't want to crash anymore......
here is a backtrace, i hope it help you

Revision history for this message
Pauli (paniemin) wrote :

Seems like this is related to bugs in network_worker.cpp.

Did it ever crash when you first time connected to any server? (if yes then this is _not_ networking thread freeing bug)

So it is very likely that bug was fixed when wesnoth was upgraded from 1.4.4 to 1.4.5.

Revision history for this message
Gabe Gorelick (gabegorelick) wrote :

Closing this bug since it seems to be fixed.

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