wallet: Warn on unexpected EOF while salvaging wallet#7537
Merged
laanwj merged 1 commit intobitcoin:masterfrom Feb 29, 2016
Merged
wallet: Warn on unexpected EOF while salvaging wallet#7537laanwj merged 1 commit intobitcoin:masterfrom
laanwj merged 1 commit intobitcoin:masterfrom
Conversation
Check for EOF before every getline, and warn when reading gets to EOF before the end of the data. Stricter error checking could shed more light on issues such as bitcoin#7463 and bitcoin#7379.
laanwj
force-pushed
the
2016_02_salvage_unexpected_eof
branch
from
8569580 to
ca8fb59
Compare
Contributor
|
utACK |
Member
|
utACK ca8fb59 Edit: I got this once now: |
laanwj
added a commit
that referenced
this pull request
Feb 29, 2016
ca8fb59 wallet: Warn on unexpected EOF while salvaging wallet (Wladimir J. van der Laan)
codablock
pushed a commit
to codablock/dash
that referenced
this pull request
Dec 11, 2017
…llet ca8fb59 wallet: Warn on unexpected EOF while salvaging wallet (Wladimir J. van der Laan)
random-zebra
added a commit
to PIVX-Project/PIVX
that referenced
this pull request
Nov 15, 2020
…refactor. 58504c2 [Wallet] refactor CWallet/CWalletDB/CDB (Round 2) (furszy) c16390d [Wallet] refactor CWallet/CWalletDB/CDB (Round 1) (furszy) 99adac0 C++11: s/boost::scoped_ptr/std::unique_ptr/ (furszy) 815773e use constant references for strings in functions in wallet/*.* (furszy) 24f1041 Do not shadow variables. (Pavel Janík) 6a0c59a wallet: Warn on unexpected EOF while salvaging wallet (Wladimir J. van der Laan) 12bc297 dbwrapper: Use new .data() method of CDataStream (Wladimir J. van der Laan) b0f0d91 streams: Remove special cases for ancient MSVC (Wladimir J. van der Laan) ba96777 streams: Add data() method to CDataStream (Wladimir J. van der Laan) 6ec0722 wallet: Use CDataStream.data() (Wladimir J. van der Laan) ca1a3b0 [Wallet] remove unused code/conditions in ReadAtCursor (Jonas Schnelli) fd259f3 remove unused classes from db.h (Philip Kaufmann) Pull request description: Upgrading the wallet, wallet db and db wrapper areas with several back ports and updates adaptations. List of PRs: * dashpay#5933 * bitcoin#7537 * bitcoin#8191 * bitcoin#8564 * bitcoin#8574 * bitcoin#8629 * bitcoin#9353 Note: Low priority PR, can be reviewing after merge Sapling and tier two PRs. I made it because we are pretty far from upstream in the db area and want to introduce some new functionality in the future that requires a more up-to-date db layer. ACKs for top commit: random-zebra: ACK 58504c2 and merging... Tree-SHA512: e5a700e855bcec20f0b74e41825ddc3a36b56a0cbe83212c93d212c06765254464999567b395584dfeb9d4b12999bc835d2e89949684d64b1503db36c53fd3c8
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
4 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Check for EOF before every getline, and warn when reading gets to EOF before the end of the data.
Also check when number of keys does not match number of values.
Stricter error checking could shed more light on issues such as #7463 and #7379.