Skip site navigation (1)Skip section navigation (2)
Date:      Tue, 27 Jan 2015 16:29:55 +0000
From:      bugzilla-noreply@freebsd.org
To:        freebsd-ports-bugs@FreeBSD.org
Subject:   [Bug 197125] net-p2p/transmission-daemon-2.84_1 Segmentation Fault with signal 10 or 11
Message-ID:  <bug-197125-13@https.bugs.freebsd.org/bugzilla/>

next in thread | raw e-mail | index | archive | help
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=197125

            Bug ID: 197125
           Summary: net-p2p/transmission-daemon-2.84_1 Segmentation Fault
                    with signal 10 or 11
           Product: Ports & Packages
           Version: Latest
          Hardware: amd64
                OS: Any
            Status: New
          Severity: Affects Many People
          Priority: ---
         Component: Individual Port(s)
          Assignee: freebsd-ports-bugs@FreeBSD.org
          Reporter: b.manas.88@gmail.com

Hello,

Me and a few other users of transmission-daemon have noticed a problem with the
port where the program will experience a segmentation fault and will write a
core dump to the filesystem.

There does not seem to be a particular way to cause this issue to occur. I have
experienced it at times where I was downloading torrents and also at times when
the torrent client was simply seeding. I suppose the way to reproduce this
problem would be to start the client, load up a number of torrents and wait for
it to segfault.

I have compiled the port with symbols and this is what the backtrace shows:
#0  0x0000000800e9efe7 in UTPSocket::selective_ack () from
/usr/local/lib/libutp.so.0
Cannot access memory at address 0xf5110000f51a

If you would like additional information just let me know, thanks.

Manas

-- 
You are receiving this mail because:
You are the assignee for the bug.



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?bug-197125-13>