Ubuntu
transmission package

transmission-gtk crashed with SIGSEGV in tr_torrentGetPeerId()

Bug #1196544 reported by digc16 on 2013-07-01

48

This bug affects 6 people

Affects		Status	Importance	Assigned to	Milestone
	Transmission	Unknown	Unknown	transmission-trac #5451
	transmission (Ubuntu)	In Progress	Medium	Unassigned	Ubuntu ubuntu-15.08

Bug Description

Torrents were downloading. Then it greyed out, and then it crashed. It asked to relaunch, and immediately crashed again. Maybe a bad torrent? I'm not sure, but just incase I reported it. Good luck! :)

ProblemType: Crash
DistroRelease: Ubuntu 13.10
Package: transmission-gtk 2.80-0ubuntu1
ProcVersionSignature: Ubuntu 3.10.0-1.8-generic 3.10.0-rc7
Uname: Linux 3.10.0-1-generic x86_64
ApportVersion: 2.10.2-0ubuntu3
Architecture: amd64
Date: Mon Jul 1 09:57:16 2013
EcryptfsInUse: Yes
ExecutablePath: /usr/bin/transmission-gtk
InstallationDate: Installed on 2013-06-10 (20 days ago)
InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Alpha amd64 (20130609)
MarkForUpload: True
ProcCmdline: /usr/bin/transmission-gtk magnet:?xt=urn:btih:FC26E2B72BE9F100A9C3E7D93174855D00493887&dn=dexter+s08e01+hdtv+x264+2hd+eztv&tr=udp%3A%2F%2Ffr33domtracker.h33t.com%3A3310%2Fannounce&tr=udp%3A%2F%2Fopen.demonii.com%3A1337
ProcEnviron:
LANGUAGE=en_US
PATH=(custom, no user)
XDG_RUNTIME_DIR=<set>
LANG=en_US.UTF-8
SHELL=/bin/bash
SegvAnalysis:
Segfault happened at: 0x7fea2e8e4b09 <tr_torrentGetPeerId+9>: cmpb $0x0,0x1e0(%rdi)
PC (0x7fea2e8e4b09) ok
source "$0x0" ok
destination "0x1e0(%rdi)" (0x000001e0) 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:
tr_torrentGetPeerId ()
?? ()
?? ()
?? ()
UTP_ProcessIncoming(UTPSocket*, unsigned char const*, unsigned long, bool) ()
Title: transmission-gtk crashed with SIGSEGV in tr_torrentGetPeerId()
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo

Tags:

Revision history for this message

digc16 (tribletsurvivor) wrote on 2013-07-01:

#1

Dependencies.txt Edit (7.4 KiB, text/plain; charset="utf-8")
Disassembly.txt Edit (1.1 KiB, text/plain; charset="utf-8")
ProcMaps.txt Edit (67.4 KiB, text/plain; charset="utf-8")
ProcStatus.txt Edit (845 bytes, text/plain; charset="utf-8")
Registers.txt Edit (773 bytes, text/plain; charset="utf-8")
Stacktrace.txt Edit (1.1 KiB, text/plain; charset="utf-8")
ThreadStacktrace.txt Edit (4.6 KiB, text/plain; charset="utf-8")

Revision history for this message

Apport retracing service (apport) wrote on 2013-07-01:

#2

StacktraceTop:
tr_torrentGetPeerId (tor=0x0) at torrent.c:202
buildHandshakeMessage (buf=buf@entry=0x7fea19703670 "", handshake=<optimized out>, handshake=<optimized out>) at handshake.c:197
readIA (inbuf=0x7fea1004e2e0, handshake=0x7fea1126ef80) at handshake.c:923
canRead (io=<optimized out>, arg=0x7fea1126ef80, piece=<optimized out>) at handshake.c:1011
canReadWrapper (io=0x7fea110fef90) at peer-io.c:206

Revision history for this message

Apport retracing service (apport) wrote on 2013-07-01: Stacktrace.txt

#3

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

Revision history for this message

Apport retracing service (apport) wrote on 2013-07-01: ThreadStacktrace.txt

#4

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

Changed in transmission (Ubuntu):
importance:	Undecided → Medium
tags:	removed: need-amd64-retrace

Revision history for this message

Seth Arnold (seth-arnold) wrote on 2013-07-01:

#5

Thanks for reporting this; are you in a position to be able to report this upstream? I couldn't find any immediately obvious problems reading through the source code, and upstream developers will be more familiar with the problem at hand.

If you're not able, please let me know, and I'll try to follow up upstream.

Thanks.

Revision history for this message

Marc Deslauriers (mdeslaur) wrote on 2013-07-05: Bug is not a security issue

#6

Thanks for taking the time to report this bug and helping to make Ubuntu better. We appreciate the difficulties you are facing, but this appears to be a "regular" (non-security) bug. I have unmarked it as a security issue since this bug does not show evidence of allowing attackers to cross privilege boundaries nor directly cause loss of data/privacy. Please feel free to report any other bugs you may find.

information type:

Private Security → Public

Revision history for this message

Launchpad Janitor (janitor) wrote on 2013-07-19:

#7

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

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

Revision history for this message

Rolf Leggewie (r0lf) wrote on 2015-06-20:

#8

This was fixed upstream almost two years ago according to the upstream ticket. Code inspection revealed that for one reason or another the changeset still hasn't made it into Ubuntu, quite surprisingly.

Changed in transmission (Ubuntu):
milestone:	none → ubuntu-15.08
status:	Confirmed → In Progress

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

Bug attachments

Add attachment

Remote bug watches

transmission-trac #5451 Edit

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