transmission-qt crashed with SIGSEGV in curl_multi_cleanup()

Bug #1130995 reported by Jonathan Thomas
8
This bug affects 1 person
Affects Status Importance Assigned to Milestone
curl (Ubuntu)
New
Undecided
Unassigned

Bug Description

Probably happened during shutdown.

ProblemType: Crash
DistroRelease: Ubuntu 13.04
Package: transmission-qt 2.76-0ubuntu1
ProcVersionSignature: Ubuntu 3.8.0-6.13-generic 3.8.0-rc7
Uname: Linux 3.8.0-6-generic x86_64
ApportVersion: 2.8-0ubuntu4
Architecture: amd64
Date: Wed Feb 20 20:01:34 2013
ExecutablePath: /usr/bin/transmission-qt
InstallationDate: Installed on 2012-09-24 (149 days ago)
InstallationMedia: Kubuntu 12.04.1 LTS "Precise Pangolin" - Release amd64 (20120822.2)
MarkForUpload: True
ProcCmdline: /usr/bin/transmission-qt
ProcEnviron:
 LANGUAGE=en
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=<set>
 LANG=en_US.UTF-8
 SHELL=/bin/bash
SegvAnalysis:
 Segfault happened at: 0x7fad0289d5a0 <curl_multi_cleanup+176>: mov %rax,(%rdi)
 PC (0x7fad0289d5a0) ok
 source "%rax" ok
 destination "(%rdi)" (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/x86_64-linux-gnu/libcurl-gnutls.so.4
 ?? ()
 ?? ()
 start_thread (arg=0x7face7fff700) at pthread_create.c:311
 clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:113
Title: transmission-qt crashed with SIGSEGV in curl_multi_cleanup()
UpgradeStatus: Upgraded to raring on 2012-09-25 (149 days ago)
UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo

Revision history for this message
Jonathan Thomas (echidnaman) wrote :
information type: Private → Public
Revision history for this message
Daniel Letzeisen (dtl131) wrote :

The issue is with curl.

affects: transmission (Ubuntu) → curl (Ubuntu)
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.