transmission-gtk crashed with SIGSEGV in curl_multi_cleanup()
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| transmission (Ubuntu) |
New
|
Undecided
|
Unassigned | ||
Bug Description
Trasmission, once started, stopped working
ProblemType: Crash
DistroRelease: Ubuntu 13.04
Package: transmission-gtk 2.77-0ubuntu1
Uname: Linux 3.8.2-030802-
ApportVersion: 2.9.2-0ubuntu2
Architecture: i386
CheckboxSubmission: 6eb62064dd29143
CheckboxSystem: e884839b1147d49
CrashCounter: 1
Date: Sat Mar 23 20:16:01 2013
ExecutablePath: /usr/bin/
InstallationDate: Installed on 2011-05-14 (678 days ago)
InstallationMedia: Ubuntu-Netbook 10.10 "Maverick Meerkat" - Release i386 (20101007)
MarkForUpload: True
ProcCmdline: transmission-gtk /home/username/
SegvAnalysis:
Segfault happened at: 0xb6c90dc9 <curl_multi_
PC (0xb6c90dc9) ok
source "%edx" ok
destination "(%eax)" (0x00000000) not located in a known VMA region (needed writable region)!
Stack memory exhausted (SP below stack segment)
SegvReason: writing NULL VMA
Signal: 11
SourcePackage: transmission
StacktraceTop:
curl_multi_cleanup () from /usr/lib/
?? ()
?? ()
start_thread () from /lib/i386-
clone () from /lib/i386-
ThreadStacktrace:
.
Thread 7 (Thread 0xb46a0880 (LWP 3109)):
#0 0xb7655424 in __kernel_vsyscall ()
No symbol table info available.
Cannot access memory at address 0xbf9fd8f0
Title: transmission-gtk crashed with SIGSEGV in curl_multi_
UpgradeStatus: Upgraded to raring on 2013-02-02 (49 days ago)
UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare
| Lorenzo Iannucci (iannu1997) wrote | #1 |
| Apport retracing service (apport) wrote This bug is a duplicate | #2 |
| information type: | Private → Public |
| tags: | removed: need-i386-retrace |
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 #1124508, 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.