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

logging: backend inconsistency with console and shell #27596

Closed
pabigot opened this issue Aug 15, 2020 · 2 comments
Closed

logging: backend inconsistency with console and shell #27596

pabigot opened this issue Aug 15, 2020 · 2 comments
Assignees
Labels
area: Logging bug The issue is a bug, or the PR is fixing a bug priority: low Low impact/importance bug Stale

Comments

@pabigot
Copy link
Collaborator

pabigot commented Aug 15, 2020

If you have both a console and a shell, the log messages go to the shell UART rather than the console.

If you have both CONFIG_SHELL_LOG_BACKEND=y and CONFIG_LOG_BACKEND_UART=y set the log messages go only to the console, though they are both listed as enabled back-ends in the shell.

@pabigot pabigot added bug The issue is a bug, or the PR is fixing a bug area: Logging labels Aug 15, 2020
@MaureenHelm MaureenHelm added the priority: low Low impact/importance bug label Aug 18, 2020
@github-actions
Copy link

This issue has been marked as stale because it has been open (more than) 60 days with no activity. Remove the stale label or add a comment saying that you would like to have the label removed otherwise this issue will automatically be closed in 14 days. Note, that you can always re-open a closed issue at any time.

@github-actions github-actions bot added the Stale label Oct 18, 2020
@pabigot pabigot removed the Stale label Oct 18, 2020
@github-actions
Copy link

This issue has been marked as stale because it has been open (more than) 60 days with no activity. Remove the stale label or add a comment saying that you would like to have the label removed otherwise this issue will automatically be closed in 14 days. Note, that you can always re-open a closed issue at any time.

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 Stale
Projects
None yet
Development

No branches or pull requests

3 participants