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

[nrf toup] VerifyOrDie logging for constrained devices #465

Merged
merged 1 commit into from
Jul 25, 2024

Conversation

Damian-Nordic
Copy link
Contributor

  1. Add the configuration to enable logging the location of a failed VerifyOrDie() without logging the condition to reduce the code size impact but still be able to debug failing VerifyOrDie() conditions.
  2. Allow to override FILE macro with FILE_NAME by setting the warn_builtin_macro_redefined GN arg to false to further reduce the code size increase.
  3. Add Kconfigs for nRF Connect platform for enabling both features.

1. Add the configuration to enable logging the location of
   a failed VerifyOrDie() without logging the condition to
   reduce the code size impact but still be able to debug
   failing VerifyOrDie() conditions.
2. Allow to override __FILE__ macro with __FILE_NAME__ by
   setting the warn_builtin_macro_redefined GN arg to false
   to further reduce the code size increase.
3. Add Kconfigs for nRF Connect platform for enabling both
   features.

Signed-off-by: Damian Krolik <damian.krolik@nordicsemi.no>
@Damian-Nordic Damian-Nordic merged commit 4fd4724 into nrfconnect:master Jul 25, 2024
9 checks passed
@Damian-Nordic Damian-Nordic deleted the verify_or_die branch July 25, 2024 14:07
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