Yes. You can run doxygen from ktorrent folder or you can use KDevelop to do it for you.

I can't reproduce this problem.

This is really strange indeed...

Oh wells, do you mind pointing out which class prints the "refreshing bucket" message, and the class that controls the flow of the DHT function? Thanks!

This is part of the DHT class in the function refreshBucket.

ktorrent/libktorrent/kdamlia/rpcserver.cpp in function: void RPCServer::readPacket()

Running KTorrent in debug mode, it seems that the 100% CPU usage happens because it's being bombarded with ping requests messages in the RPCServer (handled by readPacket()) non-stop, hence I'm seeing hundreds of: "DHT: Sending ping response" in the debug output (it wasn't in the logviewer).

Occassionally, in between the huge amounts of "DHT: Sending ping response" in the output, I see the output that I posted earlier. Are any of those logviewer outputs normal? I asked because:

In KTorrent A, I put a breakpoint on line 122 of rpcserver.cpp, the "msg->apply" line, and I let KTorrent B run normally with DHT (in another user's session). Naturally, when it came to the breakpoint, KTorrent A paused, and the CPU usage stayed normal. However, KTorrent B still outputs all those things I posted earlier in the logviewer (lots of "Cannot find RPC call", "DHT: Got findNode request" and "DHT: Got getPeers request"). And it doesn't stop doing that even after I close KTorrent A.

Btw, are the pings done over the network? Because even when being bombarded by hundreds of ping requests, my network traffic seemed normal.

kg wrote:ktorrent/libktorrent/kdamlia/rpcserver.cpp in function: void RPCServer::readPacket()

Running KTorrent in debug mode, it seems that the 100% CPU usage happens because it's being bombarded with ping requests messages in the RPCServer (handled by readPacket()) non-stop, hence I'm seeing hundreds of: "DHT: Sending ping response" in the debug output (it wasn't in the logviewer).

Occassionally, in between the huge amounts of "DHT: Sending ping response" in the output, I see the output that I posted earlier. Are any of those logviewer outputs normal? I asked because:

What you posted earlier is normal output.

In KTorrent A, I put a breakpoint on line 122 of rpcserver.cpp, the "msg->apply" line, and I let KTorrent B run normally with DHT (in another user's session). Naturally, when it came to the breakpoint, KTorrent A paused, and the CPU usage stayed normal. However, KTorrent B still outputs all those things I posted earlier in the logviewer (lots of "Cannot find RPC call", "DHT: Got findNode request" and "DHT: Got getPeers request"). And it doesn't stop doing that even after I close KTorrent A.

So A is apparently bombarded with pings and other DHT messages.

Btw, are the pings done over the network? Because even when being bombarded by hundreds of ping requests, my network traffic seemed normal.

All pings are over the network, you should run ethereal and see where these messages come from and how many there are. All DHT packets are UDP.