Provides steps to attach debugger to CAPRKE2 #576
Merged
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
dharmit
force-pushed
the
attach-debugger
branch
from
7565c7e to
889aeff
Compare
dharmit
force-pushed
the
attach-debugger
branch
from
889aeff to
7036024
Compare
kkaempf
added
kind/enhancement
alexander-demicev
approved these changes
Feb 19, 2025
yiannistri
approved these changes
Feb 19, 2025
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.
What this PR does / why we need it:
Lays out the steps to attach debugger to a CAPRKE2 process running in developer setup. We need it for easier troubleshooting/debugging on part of the developers.
Which issue(s) this PR fixes:
Fixes # NA
Special notes for your reviewer:
Checklist: