amule crashed with SIGSEGV in g_source_remove()
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
amule (Ubuntu) |
New
|
Undecided
|
Unassigned |
Bug Description
seems like a duplicate of another bug which crashes aMule permanently - when will this be fixed???
it is LTS...
?
ProblemType: Crash
DistroRelease: Ubuntu 14.04
Package: amule 2.3.1-11
ProcVersionSign
Uname: Linux 3.19.0-31-generic x86_64
ApportVersion: 2.14.1-0ubuntu3.17
Architecture: amd64
CrashCounter: 1
CurrentDesktop: XFCE
Date: Sun Oct 25 20:22:15 2015
ExecutablePath: /usr/bin/amule
InstallationDate: Installed on 2015-06-25 (122 days ago)
InstallationMedia: Xubuntu 14.04.2 LTS "Trusty Tahr" - Release amd64 (20150218.1)
ProcCmdline: amule
SegvAnalysis:
Segfault happened at: 0x7f0e74ecc8f3 <malloc_
PC (0x7f0e74ecc8f3) ok
source "0x18(%rax)" (0x00000018) not located in a known VMA region (needed readable region)!
destination "%rbx" ok
Stack memory exhausted (SP below stack segment)
SegvReason: reading NULL VMA
Signal: 11
SourcePackage: amule
StacktraceTop:
?? () from /lib/x86_
?? () from /lib/x86_
g_source_remove () from /lib/x86_
GSocketGUIFunc
GSocket:
Title: amule crashed with SIGSEGV in g_source_remove()
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
Thank you for taking the time to report this crash and helping to make this software better. This particular crash has already been reported and is a duplicate of bug #1156582, so is being marked as such. Please look at the other bug report to see if there is any missing information that you can provide, or to see if there is a workaround for the bug. Additionally, any further discussion regarding the bug should occur in the other report. Please continue to report any other bugs you may find.