Registered Member
|
This time I made sure to build with full debug info, and ran it in gdb, with the kde crash handler off (it cant seem to get debug info when ktorrent crashed, dunno why)
|
Moderator
|
|
Registered Member
|
|
Registered Member
|
Two issues, on startup I get allot of these:
and On exit, ktorrent crashes, but not in gdb, which makes me think it might be some uninitilized variables, but I can't be sure. And ktorrent is taking forever to launch in valgrind... |
Registered Member
|
Ok, here we go, valgrind results:
|
Moderator
|
|
Registered Member
|
so far ktorrent is the slowest I've ever seen in valgrind.
How about the invalid reads and writes in the dht code? ie:
That seems to coincide with the crashes I've seen on exiting ktorrent. (I recall hearing that other people I talk to have the same crash on exit, and one mentioned that stopping torrents before exiting helps, don't know for sure though) Though since that last svn up I did, it hasn't crashed at runtime, which is good. I do believe it still crashes on exit, but not in gdb, and kde's crash dialog never returns valid info when ktorrent crashes. |
Moderator
|
Registered users: Bing [Bot], Evergrowing, Google [Bot]