segfault on wallet_import_private_key #253
Comments
Note: if I first add the corresponding public key using
|
Note: this was done in a VPS, tried rebooting, fresh git pull, rm ~/.BitshareXTS, always happen the same way. Tried it in a virtual box, and I don't get the segfault but the other message about error parsing WIF private key. The other weird thing is that it is listed correctly after that using This all seems to hint at memory corruption that seems to happen somewhere, so I tried running it in valgrind, but that didn't help as there are too many other warning about uninitialized values and invalid reads (mostly from leveldb) and then some more where valgrind seems to lose track of things completely... Let me know if there's anything I can do to help debug this. |
tried new stack trace:
tried also with |
This seems to be related to a debian/ubuntu issue... On the 3 debian systems I tried it fails whereas on ubuntu I can correctly import 4 keys (and the last one is probably not registered). |
Found it! It was a problem with gcc 4.7, recompiling with gcc 4.8 solved all my issues... |
I am part of the delegates for the dry run, but I get a segfault when importing any of the private keys that correspond to the public ones I gave on bitsharestalk.
I am on commit 339072b
Stacktrace:
The text was updated successfully, but these errors were encountered: