Published on: 2014-06-03T17:40:38+00:00
On June 2nd, 2014, Toshi Morita reported an uninitialized memory problem in the bitcoind software using valgrind. The error message indicated that there was a conditional jump or move in the program that depended on uninitialised value(s). The specific function where the error occurred was CWallet::LoadKeyMetadata in wallet.cpp, which is responsible for loading key metadata from the wallet database. Upon further investigation, it was found that the error originated from the ReadKeyValue function in walletdb.cpp, which is used to read data from the wallet database. This function is then called by CWalletDB::LoadWallet, and subsequently by CWallet::LoadWallet(bool&), both located in wallet.cpp. These functions are called by AppInit2 in init.cpp, and ultimately by the main function of the application, AppInit in bitcoind.cpp.Jeff Garzik, a Bitcoin core developer and open-source evangelist at BitPay Inc., responded to Toshi's email and expressed that he believes he has identified the issue. He mentioned that one side of the comparison had been fixed but the other still had the same problem. Toshi confirmed this and stated that he would investigate further once he was out of meetings or meeting preparations.In addition to the discussion about the uninitialized memory problem, Jeff also shared information about a new guide to graph databases called "Graph Databases" that can be downloaded for free. He ended the conversation by mentioning that he is a Bitcoin core developer and an open-source evangelist at BitPay Inc.Overall, the email conversation provides insights into the uninitialized memory problem in the bitcoind software, with Toshi reporting the issue, Jeff identifying the potential cause, and plans for further investigation.
Updated on: 2023-08-01T09:25:31.724962+00:00