Add script which injects DSO into NodeJS process #438
Closed
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
Jongy
reviewed
Aug 12, 2022
Jongy
reviewed
Aug 12, 2022
Jongy
reviewed
Aug 12, 2022
Jongy
reviewed
Aug 12, 2022
Jongy
reviewed
Aug 12, 2022
Jongy
reviewed
Aug 12, 2022
Jongy
reviewed
Aug 12, 2022
Jongy
reviewed
Aug 12, 2022
Jongy
reviewed
Aug 12, 2022
Contributor
|
@kwisniewski98 as discussed, we should try to get a full flow working (with the DSO from node-linux-perf) and test it on container & non container nodejs apps. Then once we know that all parts connect well, we can focus on creating the jitdump DSO. |
Contributor
|
Superseded by #451, all comments were resolved / moved there. Closing this |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
Description
Script assumes that you have already compiled linux-perf module and takes path to it as argument. Script can be easily modified to load any module, it is focused on that particular module only by running
start()on it. In future this should be part of NodeJS profiler, but for now it is only standalone script.Related Issue
#418
Motivation and Context
In current state, gProfiler cannot profile NodeJS without restarting it. Functions from that script will allow it to attach to NodeJS process and enable generating debug symbols.
How Has This Been Tested?
Tested manually on app with CommonJS entry script
Checklist: