wallet: Use fsbridge::ifstream to fix Windows path issue#15468
wallet: Use fsbridge::ifstream to fix Windows path issue#15468laanwj merged 1 commit intobitcoin:masterfrom ken2812221:win-wallet-fix
Conversation
|
utACK 6ad79cb |
ryanofsky
left a comment
There was a problem hiding this comment.
utACK 6ad79cb. I was going to suggest that maybe there should be a linter only allowing use of fsbridge::ifstream, and not other ifstream classes. But this might be too strict because in a lot of cases we can know that filename being opened is ascii.
|
Gitian builds for commit b4fc525 (master):
Gitian builds for commit fef7c84b5f7fbda799c55888f05fd7f06d5e5705 (master and this pull):
|
|
utACK 6ad79cb |
File system access should always go through the fsbridge when possible, this is better for sandboxing. So I think this would be appropriate, as well as mentioning this in the developer notes of course. |
Summary: ``` If compiled with mingw, use glibc++ extension stdio_filebuf to open the file by FILE* instead of filename. In other condition, we can use boost::fstream. ``` Backport of core [[bitcoin/bitcoin#13878 | PR13878]] and [[bitcoin/bitcoin#15468 | PR15468]] (related bug fix). Depends on D5539. Test Plan: ninja check make check Run the Gitian builds. Build and run for Windows. Run `test_bitcoin` on Windows. Reviewers: #bitcoin_abc, jasonbcox Reviewed By: #bitcoin_abc, jasonbcox Differential Revision: https://reviews.bitcoinabc.org/D5539
…th issue 6ad79cb wallet: Use fsbridge::ifstream to fix Windows path issue (Chun Kuan Lee) Pull request description: Fix bitcoin#15460 Tree-SHA512: 1dab04184608543d49c86cbcfb679d63d35cb7bf3bde2e2d9ddf25ec8977de42b7131db5e81a305f3452858079dbcf68f6ad4624c89575d3d7e5b550687fc6ad

Fix #15460