mirror/bitcoin
1
0 Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

Fix a few likely documentation typos

Browse Source
This commit is contained in:
Lőrinc committed 2024-08-28 15:13:52 +02:00
1 parent 0c90fc6443
commit 7ee5c3c5b2
2 files changed
+6 -6
Download Patch File Download Diff File Expand all files Collapse all files

No files matched your search

doc/build-windows-msvc.md
+1 -1
View File
@@ -46,7 +46,7 @@ cmake --list-presets
CMake will put the resulting object files, libraries, and executables into a dedicated build directory. CMake will put the resulting object files, libraries, and executables into a dedicated build directory.
In following istructions, the "Debug" configuration can be specified instead of the "Release" one. In the following instructions, the "Debug" configuration can be specified instead of the "Release" one.
### 4. Building with Dynamic Linking with GUI ### 4. Building with Dynamic Linking with GUI
src/test/README.md
+5 -5
View File
@@ -17,7 +17,7 @@ during the generation of the Bitcoin Core build system
and tests weren't explicitly disabled. and tests weren't explicitly disabled.
Assuming the build directory is named `build`, the unit tests can be run Assuming the build directory is named `build`, the unit tests can be run
with `ctests --test-dir build`, which includes unit tests from subtrees. with `ctest --test-dir build`, which includes unit tests from subtrees.
To run the unit tests manually, launch `build/src/test/test_bitcoin`. To recompile To run the unit tests manually, launch `build/src/test/test_bitcoin`. To recompile
after a test file was modified, run `cmake --build build` and then run the test again. If you after a test file was modified, run `cmake --build build` and then run the test again. If you
@@ -83,7 +83,7 @@ so no leftover state is used.)
```bash ```bash
$ build/src/test/test_bitcoin --run_test=getarg_tests/doubledash -- -testdatadir=/somewhere/mydatadir $ build/src/test/test_bitcoin --run_test=getarg_tests/doubledash -- -testdatadir=/somewhere/mydatadir
Test directory (will not be deleted): "/somewhere/mydatadir/test_common_Bitcoin Core/getarg_tests/doubledash/datadir Test directory (will not be deleted): "/somewhere/mydatadir/test_common_Bitcoin Core/getarg_tests/doubledash/datadir"
Running 1 test case... Running 1 test case...
*** No errors detected *** No errors detected
@@ -112,8 +112,8 @@ see `uint256_tests.cpp`.
### Logging and debugging in unit tests ### Logging and debugging in unit tests
`ctest --test-dir build` will write to a log file `build/Testing/Temporary/LastTest.log`. You can `ctest --test-dir build` will write to the log file `build/Testing/Temporary/LastTest.log`. You can
additionaly use the `--output-on-failure` option to display logs of the failed tests automatically additionally use the `--output-on-failure` option to display logs of the failed tests automatically
on failure. For running individual tests verbosely, refer to the section on failure. For running individual tests verbosely, refer to the section
[above](#running-individual-tests). [above](#running-individual-tests).
@@ -150,5 +150,5 @@ You can then explore the core dump using
```bash ```bash
gdb build/src/test/test_bitcoin core gdb build/src/test/test_bitcoin core
(gbd) bt # produce a backtrace for where a segfault occurred (gdb) bt # produce a backtrace for where a segfault occurred
``` ```