[WIP] add DEBUGGING readme with decode of kernel call trace #55
Conversation
This file contains 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
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.
I tried to start to do a readme for debugging, as I think is important and useful for user (major don't have enough knowledge) and also for developer have more info that help to solve bugs or unexpected cases.
I started to put some info related to decode kernel call trace, probably is not explain good (my english is bad and I'm also not good at explaining) and important informations are missed.
Probably is good add info also about other distros kernel and how to use debuginfod (for some distro official kernel is supported) that should avoid install some gb of debug kernel packages but I not used it for now.
Any help is appreciated.