Skip to content
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

Save interpreter_base and ld_path at AddressSpace construction. #2747

Merged
merged 2 commits into from
Nov 21, 2020

Conversation

bernhardu
Copy link
Contributor

This aids compatibility with GDB 10.1.
Related issue #2740.

This aids compatibility with GDB 10.1.
Related issue rr-debugger#2740.
@rocallahan
Copy link
Collaborator

This looks good. Ideally we'd also have a test for this. The test would use iterate_maps to search for the interpreter mapping and unmap its first page, I guess, and we'd need a gdb script.

@rocallahan
Copy link
Collaborator

I think in this case I'm going to ask nicely for a test but not require it if it's too hard.

@bernhardu
Copy link
Contributor Author

Let me have a look, but might take some time.

@bernhardu bernhardu changed the title Save interpreter_base and ld_path at AddressSpace construction. WIP: Save interpreter_base and ld_path at AddressSpace construction. Nov 20, 2020
Retrieving the interpreter_base fails if done after
interpreter gets invalidated.
Related to rr-debugger#2740
@bernhardu bernhardu changed the title WIP: Save interpreter_base and ld_path at AddressSpace construction. Save interpreter_base and ld_path at AddressSpace construction. Nov 20, 2020
@bernhardu
Copy link
Contributor Author

The added test invalid_interpreter fails at x86_64 if the first patch to rr is not applied, but succeeds if both patches are applied.
The test invalid_interpreter-32 succeeded already before.
Is this somewhere near what you had in mind?

@rocallahan rocallahan merged commit 79ac37a into rr-debugger:master Nov 21, 2020
@rocallahan
Copy link
Collaborator

Great thanks.

@bernhardu bernhardu deleted the 2740-gdb101-2 branch March 20, 2024 09:24
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants