From c4b57963eee7843db85bcdaf16cbd36b1517dde5 Mon Sep 17 00:00:00 2001 From: Robert Schmidt Date: Thu, 23 Jan 2025 14:15:51 +0100 Subject: [PATCH] Add some documentation on debug flags/dump --- common/utils/LOG/DOC/rtusage.md | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/common/utils/LOG/DOC/rtusage.md b/common/utils/LOG/DOC/rtusage.md index b3de6cd71e..7d5bd94b8c 100644 --- a/common/utils/LOG/DOC/rtusage.md +++ b/common/utils/LOG/DOC/rtusage.md @@ -228,6 +228,10 @@ It can also be retrieved when using the telnet server, as explained [below](### | `_debug` | `boolean` | 0 = false | Triggers the activation of conditional code identified by the specified flag. | `_dump` | `boolean` | 0 = false| Triggers buffer dump, on the console in text form or in a file in matlab format, depending on the developper choice and forcasted usage| +Example: dump all ASN.1 structures during operation with +`--log_config.ASN1_debug`. To get a list of all flag/dump options, provide an +invalid flag, e.g. `--log_config.HELP_debug`. + ### Using the configuration file to configure the logging facility The following example sets all components log level to info, exept for hw,phy,mac,rlc,pdcp,rrc which log levels are set to error or warning. ```bash