diff options
| author | Jon Atack <jon@atack.com> | 2022-04-04 13:13:42 +0200 |
|---|---|---|
| committer | Jon Atack <jon@atack.com> | 2022-05-20 12:48:17 +0200 |
| commit | bd5dbc30dbef10f0fb4508b461e77787213aa0de (patch) | |
| tree | 0fc64480005cc4d040b47f6f266915a160d28830 /doc | |
| parent | 345647c4da12b5a0f9c6fd7e519df743264f5611 (diff) | |
doc: update developer notes wrt --enable-debug and DEBUG_LOCKCONTENTION
Diffstat (limited to 'doc')
| -rw-r--r-- | doc/developer-notes.md | 6 |
1 files changed, 4 insertions, 2 deletions
diff --git a/doc/developer-notes.md b/doc/developer-notes.md index ddbbd0709b..3793fb3315 100644 --- a/doc/developer-notes.md +++ b/doc/developer-notes.md @@ -394,8 +394,10 @@ Defining `DEBUG_LOCKCONTENTION` adds a "lock" logging category to the logging RPC that, when enabled, logs the location and duration of each lock contention to the `debug.log` file. -To enable it, run configure with `-DDEBUG_LOCKCONTENTION` added to your -CPPFLAGS, e.g. `CPPFLAGS="-DDEBUG_LOCKCONTENTION"`, then build and run bitcoind. +The `--enable-debug` configure option adds `-DDEBUG_LOCKCONTENTION` to the +compiler flags. You may also enable it manually for a non-debug build by running +configure with `-DDEBUG_LOCKCONTENTION` added to your CPPFLAGS, +i.e. `CPPFLAGS="-DDEBUG_LOCKCONTENTION"`, then build and run bitcoind. You can then use the `-debug=lock` configuration option at bitcoind startup or `bitcoin-cli logging '["lock"]'` at runtime to turn on lock contention logging. |