Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Incorrect documentation CONFIG_LOG_STRDUP_MAX_STRING #33218

Closed
wldevries opened this issue Mar 10, 2021 · 1 comment
Closed

Incorrect documentation CONFIG_LOG_STRDUP_MAX_STRING #33218

wldevries opened this issue Mar 10, 2021 · 1 comment
Assignees
Labels
area: Logging bug The issue is a bug, or the PR is fixing a bug priority: low Low impact/importance bug

Comments

@wldevries
Copy link

Describe the bug
According to documentation CONFIG_LOG_STRDUP_MAX_STRING should default to 66 when CONFIG_BT is enabled, but it has no effect.

https://docs.zephyrproject.org/latest/reference/kconfig/CONFIG_LOG_STRDUP_MAX_STRING.html

To Reproduce
Build a sample with the following minimal prj.conf

CONFIG_BT=y
CONFIG_LOG=y

Expected behavior
I expect CONFIG_LOG_STRDUP_MAX_STRING=66 to appear in build\zephyr\.config, but it is at 32 instead.

Impact
annoyance

Logs and console output
none

Environment (please complete the following information):

  • OS: Windows 10
  • Toolchain: gnuarmemb
  • Commit SHA or Version used: ff5b040f782297003040c1dc4fe43521bc8dc052

Additional context
none

@wldevries wldevries added the bug The issue is a bug, or the PR is fixing a bug label Mar 10, 2021
@nashif nashif added priority: low Low impact/importance bug area: Logging labels Mar 12, 2021
@nordic-krch
Copy link
Contributor

Documentation is from latest master and your commit not. 66 was introduced in 8575412.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area: Logging bug The issue is a bug, or the PR is fixing a bug priority: low Low impact/importance bug
Projects
None yet
Development

No branches or pull requests

3 participants