Fixed 'info proc mappings' parsing for GDB>=12 #98
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
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.
Parsing the
info proc mappingcommand for GDB versions 12 and on is broken, since they include a perms column before the objfile column. Because everything after column 4 gets added to the name of the object, this breaks the sync functionality.This happens because the objfile name is used to verify it's actually the name of the binary, normally this would for example be /usr/bin/cat, where for GDB >=12 it turns into r--p /usr/bin/cat, which the Ghidra/IDA side sees as something else than the current binary.
Examples:
GNU gdb (Ubuntu 12.1-0ubuntu1~22.04) 12.1:
GNU gdb (Ubuntu 11.1-0ubuntu2) 11.1:
