|
Title: "cannot open wallet dump file" Post by: ArpFlush on June 08, 2015, 11:54:29 AM Hi everyone,
I'm on Testnet and trying the dumpwallet command. When I type: dumpwallet wallet.txt I get this error: "cannot open wallet dump file (code -8)" Any ideas why? ??? Thanks! Edit: It worked when I type: dumpwallet "C:\Users\myusername\Documents\Bitcoin\dumpwallet.txt" :D Title: Re: "cannot open wallet dump file" Post by: achow101_alt on June 08, 2015, 08:35:20 PM You needed to specify the path for the output file.
Title: Re: "cannot open wallet dump file" Post by: tspacepilot on June 09, 2015, 03:09:18 AM It would be nice for a future version of bitcoincore to include a text versions of the error codes so that users can interpret things like -8 means "missing path argument" or something like that without having to post here or grep through source code for the interpretations. Don't get me wrong, error codes are useful and awesome, but eventually it's nice to provide a text based version of the error code along with the numerical one. Really, the numerical one is more useful for API usage.
Title: Re: "cannot open wallet dump file" Post by: Newar on June 09, 2015, 03:27:18 AM It would be nice for a future version of bitcoincore to include a text versions of the error codes so that users can interpret things like -8 means "missing path argument" or something like that without having to post here or grep through source code for the interpretations. Don't get me wrong, error codes are useful and awesome, but eventually it's nice to provide a text based version of the error code along with the numerical one. Really, the numerical one is more useful for API usage. Open an issue on github. Title: Re: "cannot open wallet dump file" Post by: tspacepilot on June 09, 2015, 04:22:23 AM It would be nice for a future version of bitcoincore to include a text versions of the error codes so that users can interpret things like -8 means "missing path argument" or something like that without having to post here or grep through source code for the interpretations. Don't get me wrong, error codes are useful and awesome, but eventually it's nice to provide a text based version of the error code along with the numerical one. Really, the numerical one is more useful for API usage. Open an issue on github. I will do that, I'm glad you suggested it---I wouldn't have thought to do so otherwise. |