trace/dawr: Handle debuginfod check #2952
Open
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
On recent Linux distribution releases running gdb debug session with dawr binary fails. While running the program with gdb following interactive debuginfod related question is introduced Enable debuginfod for this session? (y or [n]) Handle this additional ask by extending the fedora only check to SUSE release. While at it avoid duplication of this code by moving the logic to run_cmd Signed-off-by: Sachin Sant <[email protected]>
|
Without the fix: (1/3) trace/dawr.py:Dawr.test_read_dawr_v1: STARTED With fix: (1/3) trace/dawr.py:Dawr.test_read_dawr_v1: STARTED |
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.
On recent Linux distribution releases running gdb debug session
with dawr binary fails. While running the program with gdb,
following interactive debuginfod related question is introduced
Enable debuginfod for this session? (y or [n])
Handle this additional ask by extending the fedora only check to
SUSE release. While at it avoid duplication of this code by moving
the logic to run_cmd
Signed-off-by: Sachin Sant [email protected]