-
Notifications
You must be signed in to change notification settings - Fork 16
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
Introduced an API to collect the core from an unrelated process #11
Open
ramkums
wants to merge
1
commit into
Percona-Lab:master
Choose a base branch
from
ramkums:coredumper_tool
base: master
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
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
jlevon
suggested changes
Dec 2, 2024
jlevon
suggested changes
Dec 9, 2024
/* If pid belong to the one called the library no need to proceed */ | ||
if (expid == 0 && pid == clone_pid) continue; | ||
|
||
strcat(strcpy(fname, "/proc/"), entry->d_name); |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
it's fine
jlevon
suggested changes
Dec 10, 2024
jlevon
approved these changes
Jan 9, 2025
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
thanks, I think this looks good to me now
The API WriteCoreDumpOfPID() will take argument pid, and try to collect the core from the process with pid, this uses the existing logic to identify the threads under the given process and to identify the maps and the properties of each memory maps. Then read the memory content from /proc/[pid]/mem, we assume that the caller has the permission to trace and read the mem from process [pid]. A tool also introduced, which will use the API WriteCoreDumpOfPID and provide a convenient CLI for the user, which will help in creating core dump of any process that the user has permission to trace. Following is the help from the tool: Usage: ./coredumper_tool <-c corefile> <-p pid> [-s core_size] [-z] <-h> Show this message and exit <-c core_file> Collect the core dump into a file core_file <-p pid> Collect the core dump of process with pid <-s core_size> Limit the size of core_file to core_size <-z> Compress the core_file on the fly with gzip
ramkums
force-pushed
the
coredumper_tool
branch
from
January 13, 2025 04:54
7cc27b0
to
dd17672
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.
The API WritePidCoreDumpWith() will take argument pid, and try to collect the core from the process with pid, this uses the existing logic to identify the threads under the given process and to identify the maps and the properties of each memory maps. Then read the memory content from /proc/[pid]/mem, we assume that the caller has the permission to trace and read the mem from process [pid].
A tool also introduced, which will use the API WritePidCoreDumpWith and provide a convenient CLI for the user, which will help in creating core dump of any process that the user has permission to trace.