Parse StartCode, EndCode, and StartStack in Proc.Stat()
#659
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
Signed-off-by: Pierre Gimalac <[email protected]>
pgimalac
force-pushed
the
pgimalac/proc-stat-code-heap-fields
branch
from
15960ea
to
1992644
Compare
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.
Add the following fields to the
ProcStattype and read them from/proc/<pid>/statinProc.Stat():See fields 26, 27, and 28 in https://man7.org/linux/man-pages/man5/proc_pid_stat.5.html.
It enables categorizing regions from
/proc/<pid>/mapsdepending on their address (ie. actual code vs something else, eg. memory mapped file).