docs: enforce tracing framework over logging in CLAUDE.md #143
+107
−7
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Updates debugging guidance to make the tracing framework the MANDATORY primary approach for kernel observability: - Added 🚨 MANDATORY section explaining why logs are forbidden - Documented tracing framework usage (GDB calls, /proc interface) - Added scripts/test_tracing_via_gdb.sh to approved workflows - Demoted raw_serial_char() to "LAST RESORT" status - Added trace_dump() commands to GDB workflow examples - Added "Tracing Framework Memory Dump" section for validation Key message: DO NOT add log statements to debug kernel issues. The tracing framework exists specifically for this purpose. Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Summary
Updates CLAUDE.md to strongly emphasize that the tracing framework is the MANDATORY approach for kernel debugging and observability.
Changes
trace_dump(),trace_dump_latest(),trace_dump_counters())/proc/trace/{enable,events,buffer,counters})scripts/test_tracing_via_gdb.sh)raw_serial_char()to "LAST RESORT" statusKey Message
DO NOT add log statements to debug kernel issues. The tracing framework exists specifically for this purpose and is the ONLY acceptable approach for kernel observability.
Test plan
🤖 Generated with Claude Code