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

vmaddr or offset or both? #2

Open
m4b opened this issue Sep 22, 2015 · 0 comments
Open

vmaddr or offset or both? #2

m4b opened this issue Sep 22, 2015 · 0 comments

Comments

@m4b
Copy link
Owner

m4b commented Sep 22, 2015

Currently rdr makes bad distinctions between offsets and vmaddr. Unfortunately, our previous binary masters believed that embedding vmaddresses in the binary was the responsibility of the binary and not the loader and dynamic linker. This was foolish, but there's nothing we can do now.

So, because both have their uses, especially when debugging, a --vm switch might be a good idea to not perform automatic offset computations.

This will add complications, but might be necessary.

Alternatively, we could only return non-normalized binary offsets, and have a switch for returning binary offsets. Regardless, a consistent approach has to be taken, because right now it's a disassister, especially the --do switch.

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

No branches or pull requests

1 participant