-
-
Notifications
You must be signed in to change notification settings - Fork 734
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[Bug] read_cstring length can be set so that it reads into an unmapped region #1055
Comments
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. You can reopen it by adding a comment to this issue. |
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. You can reopen it by adding a comment to this issue. |
This issue has been automatically closed because it has not had recent activity. If you are the owner of this issue, you can either re-open it and provide a more complete description; or create a new issue. Thank you for your contributions. |
Wasn't this fixed? Will close with the proper tag |
Not yet, it's under review. |
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. You can reopen it by adding a comment to this issue. |
GEF+GDB version
Operating System
OSX
Describe the issue you encountered
When a gef.memory.maps section ends and there is a register set to a value near the end,
read_cstring
will try to read past the end of the page, into unmapped memory. This causes an error in printing the context.It seems that we can avoid this with
set mem inaccessible-by-default off
, but I am not sure we want to.We might want to instead properly set the
length
based on our memory maps.Do you read the docs and look at previously closed issues/PRs for similar cases?
No
Architecture impacted
Describe your issue. Without a proper reproduction step-by-step, your issue will be ignored.
Provide a step-by-step to reproduce your issue.
Minimalist test case
No response
Additional context?
No response
The text was updated successfully, but these errors were encountered: