-
Notifications
You must be signed in to change notification settings - Fork 60
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
gnu linker script? #62
Comments
gtirb-pprinter (which is the component responsible for generating assembly and other artifacts for re-assembly, e.g., symbol version scripts - emitting an IR from ddisasm and using gtirb-pprinter directly gives some more options than ddisasm's Is the idea of generating a linker script intended to ensure each section retains the original address? Or are there additional problems that it would solve? #59 is a related issue, which has a bit more discussion of additional challenges with regenerating binaries identical to the original (in particular, this comment from aeflores). |
Generating linker scripts could help with some of the discrepancies, and we have considered implementing this functionality (in gtirb-pprinter), but as @adamjseitz said, this is not yet supported. |
I see. Thanks.
Mostly yes. And it enables users to inject code to where they want without using pure address in assembly(which is not easy to modify)
Thanks. |
Oh, this also prevent gcc from using its default linker script which removes vanilla sections of the elf. |
can ddisasm generate a gnu linker script to ensure the reassembled binary is the same as the old one?
The text was updated successfully, but these errors were encountered: