attach: Work around a bug in old gdb versions #310
Merged
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
There's a bug (fixed in gdb 10.1) with how gdb parses the "commands" command when reading from a script, which causes the commands to get associated only with the first breakpoint rather than all of the breakpoints we wanted them associated with. Through sheer good luck, this bug doesn't affect the case when a range of breakpoint numbers is given, rather than a space separated list of breakpoint numbers, so we can switch to using a range to avoid the bug. Signed-off-by: Matt Wozniski <[email protected]>
godlygeek
force-pushed
the
work_around_gdb_bug
branch
from
2f63298
to
f8073b4
Compare
Signed-off-by: Matt Wozniski <[email protected]>
pablogsal
approved these changes
Feb 1, 2023
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.
There's a bug (fixed in gdb 10.1) with how gdb parses the "commands" command when reading from a script, which causes the commands to get associated only with the first breakpoint rather than all of the breakpoints we wanted them associated with.
Through sheer good luck, this bug doesn't affect the case when a range of breakpoint numbers is given, rather than a space separated list of breakpoint numbers, so we can switch to using a range to avoid the bug.
Signed-off-by: Matt Wozniski [email protected]
Closes #309