I'm test-running 0.7.1rc1 (self-compiled with libdb5.1 and without upnp on linux)
and found it drop dead already twice after sending it commands in the debug-console.
This (2nd) time it was the "move" command.
I instantly saw the mining-activity stop (cpu-meter in the panel), and the move
command didn't return a response. When it happened, I could still type more commands
in the console (though without getting an answer), but meanwhile also the debug-widget
has dropped dead and doesn't redraw anymore. I'll leave it stuck for a while and will look
back in this thread for debugging instructions before killing&restarting it...
PS: gdb says, it's stuck in pthreads_cond_wait in boost::unique_lock
in AddressTableModel::labelForAddress(QString)
in TransactionTableModel::lookupAddress(string,bool)
Interesting. One of my nodes has been doing the same thing in response to the RPC move command.