amuled crashed with SIGABRT in __libc_message()

[Rubén Parra]

In 12.04

ProblemType: Crash
DistroRelease: Ubuntu 12.04
Package: amule-daemon 2.3.1-1
ProcVersionSignature: Ubuntu 3.2.0-19.30-generic 3.2.11
Uname: Linux 3.2.0-19-generic x86_64
ApportVersion: 1.94.1-0ubuntu2
Architecture: amd64
Date: Tue Mar 20 18:51:05 2012
ExecutablePath: /usr/bin/amuled
ProcCmdline: amuled
Signal: 6
SourcePackage: amule
StacktraceTop:
 raise () from /lib/x86_64-linux-gnu/libc.so.6
 abort () from /lib/x86_64-linux-gnu/libc.so.6
 ?? () from /lib/x86_64-linux-gnu/libc.so.6
 __fortify_fail () from /lib/x86_64-linux-gnu/libc.so.6
 __chk_fail () from /lib/x86_64-linux-gnu/libc.so.6
Title: amuled crashed with SIGABRT in raise()
UpgradeStatus: Upgraded to precise on 2012-03-20 (0 days ago)
UserGroups: adm admin cdrom dialout disk lpadmin plugdev sambashare

[Apport retracing service (apport)]

StacktraceTop:
 __libc_message (do_abort=2, fmt=0x7fbfa992c71c "*** %s ***: %s terminated\n") at ../sysdeps/unix/sysv/linux/libc_fatal.c:201
 __GI___fortify_fail (msg=0x7fbfa992c6b3 "buffer overflow detected") at fortify_fail.c:32
 __GI___chk_fail () at chk_fail.c:29
 __fdelt_chk (d=<optimized out>) at fdelt_chk.c:26
 GSocket::Input_Timeout (this=0x7fbf9c002a40) at ../src/unix/gsocket.cpp:1561

[Launchpad Janitor (janitor)]

Status changed to 'Confirmed' because the bug affects multiple users.

[Anatol Pomozov (anatol)]

The same crash reported to amule project forum http://amule.forumer.com/amuled-crash-with-fortify-enabled-suspect-buffer-overflow-t2337957.html

[Anatol Pomozov (anatol)]

There are few findings:

1) It is a bug in wx code (GSocket) in 2.8
2) wx developers recommend to use 2.9, as socket bugs in 2.8 most likely will not be fixed
3) I compiled amule with wx 2.9 and it seems work fine (no crashes so far)

https://groups.google.com/forum/#!topic/wx-users/cGf2gdHamKs