Ready for testing: 0.7.1 release candidate 1

[arklan]

ok, regarding the URI thing: FINALLY got a successful complete sync of the main blockchain, and it worked fine. hurray!

man, virtual machines really don't like being left idle...

[1715396422]

1715396422

[1715396422]

1715396422

[1715396422]

1715396422

[AvL42]

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)

[runeks]

I get an error message saying:

Code:

Error initializing database environment /home/rune/.bitcoin!
To recover, BACKUP THAT DIRECTORY, then remove
everything from it except for wallet.dat.

Is this expected? I've had to download the block chain from scratch a couple of times previously when I've upgraded. Is it because it uses a newer version of BDB?

Here's the solution to this issue (for the record):

If you were running on Linux with a version that might have been compiled
with a different version of Berkeley DB (for example, if you were using an
Ubuntu PPA version), then run the old version again with the -detachdb
argument and shut it down; if you do not, then the new version will not
be able to read the database files and will exit with an error.

https://bitcointalk.org/index.php?topic=119277.0

[kjj]

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.

[AvL42]

indeed, also happens with RPC, not only with debug console. Not sure, though, if any other command is affected, too.