Bug 139759 - Ktorrent dies with SIGABRT
Summary: Ktorrent dies with SIGABRT
Status: RESOLVED INTENTIONAL
Alias: None
Product: ktorrent
Classification: Applications
Component: general (other bugs)
Version First Reported In: unspecified
Platform: unspecified Linux
: NOR crash
Target Milestone: ---
Assignee: Joris Guisson
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2007-01-08 08:57 UTC by Barry Schatz
Modified: 2007-03-02 15:08 UTC (History)
0 users

See Also:
Latest Commit:
Version Fixed In:
Sentry Crash Report:

Attachments
Backtrace of Ktorrent crash (4.80 KB, text/plain)
2007-01-08 09:00 UTC, Barry Schatz 		Details
View All Add an attachment

Note You need to log in before you can comment on or make changes to this bug.
Description Barry Schatz 2007-01-08 08:57:25 UTC 
Version:           2.0.3 (using KDE 3.5.5, Debian Package 4:3.5.5a.dfsg.1-5 (4.0))
Compiler:          Target: i486-linux-gnu
OS:                Linux (i686) release 2.6.18-3-686

I run Ktorrent for a few minutes, and it dies on its own.  I tried disabling several plugins, leaving the info widget and the log viewer running.  I have 52 torrents seeding and none leeching.
I have three backtraces, and I will attach the last one.
Comment 1 Barry Schatz 2007-01-08 09:00:57 UTC 
Created attachment 19182 [details]
Backtrace of Ktorrent crash
Comment 2 Joris Guisson 2007-01-08 09:47:20 UTC 
It crashes somewhere in DHT, you should try disabling DHT and see if it then keeps running.
Comment 3 Joris Guisson 2007-01-08 18:57:12 UTC 
Also giving 2.1rc1 a try, would be best, there have been many bug fixes since 2.0.3, so this might allready be fixed.
Comment 4 Barry Schatz 2007-01-08 19:24:37 UTC 
I'll try 2.1rc1.
Also, there were some torrents that were removed from the tracker.  I took them off my list and things seem more stable now.  Also, that tracker forbids dht, so maybe someone tried it and ktorrent didn't expect it.  Either way, I'll upgrade and see if you fixed the bug already.
Comment 5 Joris Guisson 2007-03-02 15:08:43 UTC 
After some investigations, this is a bug in dante, which you are using as a socks client library. At the first sign of trouble it just aborts. Doesn't even try to let the application recover.