Skip to content

logging: fix dictionary mode for dropped messages on rtt backend #94324

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

Open
wants to merge 1 commit into
base: main
Choose a base branch
from

Conversation

ksstms
Copy link

@ksstms ksstms commented Aug 11, 2025

With the dictionary feature enabled, the RTT backend would still print the "messages dropped" message as a string instead of the binary format. This commit fixes that by checking if the dictionary mode is enabled on the RTT backend, and calling the correct process function. The solution is similar to how it's done in log_backed_fs.c.

Copy link

Hello @ksstms, and thank you very much for your first pull request to the Zephyr project!
Our Continuous Integration pipeline will execute a series of checks on your Pull Request commit messages and code, and you are expected to address any failures by updating the PR. Please take a look at our commit message guidelines to find out how to format your commit messages, and at our contribution workflow to understand how to update your Pull Request. If you haven't already, please make sure to review the project's Contributor Expectations and update (by amending and force-pushing the commits) your pull request if necessary.
If you are stuck or need help please join us on Discord and ask your question there. Additionally, you can escalate the review when applicable. 😊

With the dictionary feature enabled, the RTT backend would still print
the "messages dropped" message as a string instead of the binary format.
Fix that by calling the correct process function when dictionary mode
is enabled.

Signed-off-by: Tamás Kiss <[email protected]>
@ksstms ksstms force-pushed the logging/fix-rtt-dict-dropped branch from 66cca5c to 594aa10 Compare August 11, 2025 10:08
Copy link

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants