Topic: 0.7.2rc2 needs a little testing (Read 1633 times)

You'd have to ask coderrr.
I was only making minor changes to rebase it on the latest master, not really maintaining it.

I thought it's a very popular feature used by a lot of people.
Is there a reason why Coderrr or you (I think you released a test version with the coincontrol patch) dropped this?

Only if someone is actually interested in porting it to the current code and fixing the remaining issues.
It's gone months, and nobody has stepped up.

After a first look there seem to be no major issues.
Will the coin control feature be added to the official client?
I really got used to this very useful option.

So maybe i dont know what im doing.. but I tried to follow the instructions on the 'install' file in this build.

I have bitcoind server running on a VPS, latest version of ubuntu (64 bit). Bitcoind server was running fine, until I tried the move command. Everytime I use the move command it just freezes the server and totally screws it over. Im guessing this will probably fix it, but I cant get the server to work at all now!

I copied the new bitcoind file to replace the old bitcoind file (which for me I found located in /usr/bin/bitcoin/bitcoind). I set this new file to be executable, and then tried the following:


however, when I cd in to /usr/lib/bitcoin, the file is there. I see it on my FTP client as well. Why would it be saying the file isnt there when it IS there?

Iv also tried compiling bitcoind from source. Iv installed all the dependencies that the install file says is required, and ran


seems to run fine at first, but then I get the following errors:

Then it fails.
anyone have any idea what that means?

I have been running bitcoind with the patch to fix the move bug for some time now. We use the move command quite often and haven't experienced any problems.

No, that would be a downgrade. It should still "work", but it won't use the pre0.8 blockchain and will download a 0.4-0.7-compatible one.

If i'm running sipa's pre0.8 version, can i "upgrade" and test this ?

Great work and thank you for fixing the 'move' command so quickly.  I have been working with 0.7.2rc2 on 32-bit linux for about an hour now and haven't noticed any issues.

Thanks again.

The main reason for this release is to fix a nasty bug in the RPC 'move' command that was introduced in 0.7.0.


Bitcoin version 0.7.2rc2 is now available from:
  http://sourceforge.net/projects/bitcoin/files/Bitcoin/bitcoin-0.7.2/test

This is a bug-fix minor release.

Please report bugs using the issue tracker at github:
  https://github.com/bitcoin/bitcoin/issues

How to Upgrade
--------------

If you are running an older version, shut it down. Wait
until it has completely shut down (which might take a few minutes for older
versions), then run the installer (on Windows) or just copy over
/Applications/Bitcoin-Qt (on Mac) or bitcoind/bitcoin-qt (on Linux).

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.

Explanation of -detachdb (and the new "stop true" RPC command):
The Berkeley DB database library stores data in both ".dat" and
"log" files, so the database is always in a consistent state,
even in case of power failure or other sudden shutdown. The
format of the ".dat" files is portable between different
versions of Berkeley DB, but the "log" files are not-- even minor
version differences may have incompatible "log" files. The
-detachdb option moves any pending changes from the "log" files
to the "blkindex.dat" file for maximum compatibility, but makes
shutdown much slower. Note that the "wallet.dat" file is always
detached, and versions prior to 0.6.0 detached all databases
at shutdown.

Bug fixes
---------

* Prevent RPC 'move' from deadlocking. This was caused by trying to lock the
  database twice.

* Fix use-after-free problems in initialization and shutdown, the latter of
  which caused Bitcoin-Qt to crash on Windows when exiting.

* Correct library linking so building on Windows natively works.

* Avoid a race condition and out-of-bounds read in block creation/mining code.

* Improve platform compatibility quirks, including fix for 100% CPU utilization
  on FreeBSD 9.

* A few minor corrections to error handling, and updated translations.

* OSX 10.5 supported again

----------------------------------------------------
Thanks to everybody who contributed to this release:

Alex
dansmith
Gavin Andresen
Gregory Maxwell
Jeff Garzik
Luke Dashjr
Philip Kaufmann
Pieter Wuille
Wladimir J. van der Laan
grimd34th