Bug 144971 - SIGSEGV (Signal 11), happens frequently as of late, causes crash (No user interactions, 5 big torrents (1+ GB) downloading)
Summary: SIGSEGV (Signal 11), happens frequently as of late, causes crash (No user int...
Status: RESOLVED DUPLICATE of bug 144416
Alias: None
Product: ktorrent
Classification: Applications
Component: general (show other bugs)
Version: unspecified
Platform: unspecified Linux
: NOR crash
Target Milestone: ---
Assignee: Joris Guisson
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2007-05-02 21:55 UTC by Rougald
Modified: 2007-05-03 08:50 UTC (History)
0 users

See Also:
Latest Commit:
Version Fixed In:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Rougald 2007-05-02 21:55:34 UTC
Version:           2.1 (using KDE 3.5.5, Kubuntu (edgy) 4:3.5.5-0ubuntu3.4)
Compiler:          Target: x86_64-linux-gnu
OS:                Linux (x86_64) release 2.6.17-10-generic

Happens with no user interaction, every 200 MB of DL or so.

Here is the stacktrace:


(no debugging symbols found)
Using host libthread_db library "/lib/libthread_db.so.1".
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
[Thread debugging using libthread_db enabled]
[New Thread 47519802357680 (LWP 25267)]
[New Thread 1082132816 (LWP 25294)]
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
0x00002b3810928c71 in nanosleep () from /lib/libc.so.6
#0  0x00002b3810928c71 in nanosleep () from /lib/libc.so.6
#1  0x00002b3810928a94 in sleep () from /lib/libc.so.6
#2  0x00002b380d7a8355 in KCrash::startDrKonqi ()
   from /usr/lib/libkdecore.so.4
#3  0x00002b380d7bc3c7 in KCrash::defaultCrashHandler ()
   from /usr/lib/libkdecore.so.4
#4  0x00002b38108c4510 in killpg () from /lib/libc.so.6
#5  0x0000000000000000 in ?? ()
Comment 1 Tommi Tervo 2007-05-03 08:50:57 UTC
Update to 2.1.4

*** This bug has been marked as a duplicate of 144416 ***