transmission crashed with SIGSEGV in tr_torrentNext()

Bug #446556 reported by Az
10
This bug affects 1 person
Affects Status Importance Assigned to Milestone
transmission (Ubuntu)
New
Medium
Unassigned

Bug Description

Binary package hint: transmission

Tried to close the torrent program and randomly crashed. not sure why.

ProblemType: Crash
Architecture: amd64
Date: Thu Oct 8 13:57:54 2009
DistroRelease: Ubuntu 9.10
ExecutablePath: /usr/bin/transmission
Package: transmission-gtk 1.75-0ubuntu1
ProcCmdline: transmission /tmp/Chrome_OS.i686-0.4.220.iso\ [mininova].torrent
ProcEnviron:
 LANG=en_US.UTF-8
 SHELL=/bin/bash
ProcVersionSignature: Ubuntu 2.6.31-11.38-generic
SegvAnalysis:
 Segfault happened at: 0x44b0c0 <tr_torrentNext+16>: mov 0xa8(%rdi),%rax
 PC (0x0044b0c0) ok
 source "0xa8(%rdi)" (0x000000a8) not located in a known VMA region (needed readable region)!
 destination "%rax" ok
SegvReason: reading NULL VMA
Signal: 11
SourcePackage: transmission
StacktraceTop:
 tr_torrentNext ()
 tr_torrentFindFromId ()
 ?? ()
 ?? ()
 ?? () from /usr/lib/libgdk-x11-2.0.so.0
Title: transmission crashed with SIGSEGV in tr_torrentNext()
Uname: Linux 2.6.31-11-generic x86_64
UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare

Revision history for this message
Az (azharul) wrote :
Revision history for this message
Apport retracing service (apport) wrote : Stacktrace.txt (retraced)

StacktraceTop:tr_torrentNext (session=0x0, tor=0x0)
tr_torrentFindFromId (session=0x0, id=1)
refresh (data=0x1a61e50) at file-list.c:207
refreshModel (file_data=0x0) at file-list.c:230
gdk_threads_dispatch (data=0x1aded00)

Revision history for this message
Apport retracing service (apport) wrote : ThreadStacktrace.txt (retraced)
Changed in transmission (Ubuntu):
importance: Undecided → Medium
tags: removed: need-amd64-retrace
visibility: private → public
Revision history for this message
Charles Kerr (charlesk) wrote :

Thank you for taking the time to report this bug and helping to make Ubuntu better. This particular bug has already been reported and is a duplicate of bug 319880, so it 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. Feel free to continue to report any other bugs you may find.

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.