Ubuntu
amule package

amuled crashed with SIGABRT in __libc_message()

Bug #960457 reported by Rubén Parra on 2012-03-20

38

This bug affects 6 people

Affects		Status	Importance	Assigned to	Milestone
	amule (Ubuntu)	Confirmed	Medium	Unassigned

Bug Description

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

Tags:

Revision history for this message

Rubén Parra (rubenxparra) wrote on 2012-03-20:

#1

Dependencies.txt Edit (677 bytes, text/plain; charset="utf-8")
Disassembly.txt Edit (854 bytes, text/plain; charset="utf-8")
ProcEnviron.txt Edit (232 bytes, text/plain; charset="utf-8")
ProcMaps.txt Edit (10.1 KiB, text/plain; charset="utf-8")
ProcStatus.txt Edit (818 bytes, text/plain; charset="utf-8")
Registers.txt Edit (684 bytes, text/plain; charset="utf-8")
Stacktrace.txt Edit (2.4 KiB, text/plain; charset="utf-8")
ThreadStacktrace.txt Edit (6.5 KiB, text/plain; charset="utf-8")

visibility:

private → public

Revision history for this message

Apport retracing service (apport) wrote on 2012-03-20:

#2

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

Revision history for this message

Apport retracing service (apport) wrote on 2012-03-20: Stacktrace.txt

#3

Stacktrace.txt Edit (10.1 KiB, text/plain)

Revision history for this message

Apport retracing service (apport) wrote on 2012-03-20: ThreadStacktrace.txt

#4

ThreadStacktrace.txt Edit (20.9 KiB, text/plain)

Changed in amule (Ubuntu):
importance:	Undecided → Medium
summary:	- amuled crashed with SIGABRT in raise() + amuled crashed with SIGABRT in __libc_message()
tags:	removed: need-amd64-retrace

Revision history for this message

Launchpad Janitor (janitor) wrote on 2012-03-29:

#5

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

Changed in amule (Ubuntu):
status:	New → Confirmed

Revision history for this message

Anatol Pomozov (anatol) wrote on 2013-07-13:

#6

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

Revision history for this message

Anatol Pomozov (anatol) wrote on 2013-07-13:

#7

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

Report a bug

This report contains Public information

Everyone can see this information.

Duplicates of this bug

You are

Subscribing...

Edit bug mail

Other bug subscribers

Remote bug watches

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