diff options
| author | Jon Atack <jon@atack.com> | 2022-08-20 11:09:09 +0200 |
|---|---|---|
| committer | Jon Atack <jon@atack.com> | 2022-08-20 13:40:03 +0200 |
| commit | 958048057087e6562b474f9028316c00ec03c2e4 (patch) | |
| tree | 8199547ef76c7e2f6a902f3270b57c9416d2fb63 /doc | |
| parent | 1abaa31aa3d833caf2290d6c90f57f7f79d146c0 (diff) | |
Update debug logging section in the developer notes
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 1aa4e4d690..abd6c7bb59 100644 --- a/doc/developer-notes.md +++ b/doc/developer-notes.md @@ -386,8 +386,10 @@ Run configure with the `--enable-gprof` option, then make. If the code is behaving strangely, take a look in the `debug.log` file in the data directory; error and debugging messages are written there. -The `-debug=...` command-line option controls debugging; running with just `-debug` or `-debug=1` will turn -on all categories (and give you a very large `debug.log` file). +Debug logging can be enabled on startup with the `-debug` and `-loglevel` +configuration options and toggled while bitcoind is running with the `logging` +RPC. For instance, launching bitcoind with `-debug` or `-debug=1` will turn on +all log categories and `-loglevel=trace` will turn on all log severity levels. The Qt code routes `qDebug()` output to `debug.log` under category "qt": run with `-debug=qt` to see it. |