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

Figure out a better error message when given an unstripped binary #1

Open
njsmith opened this issue Feb 15, 2016 · 0 comments
Open

Comments

@njsmith
Copy link
Owner

njsmith commented Feb 15, 2016

I'm not sure what's going on with the binaries generated by mingw-w64, but by default they contain a ton of data beyond the end of that described in the section table, and that strip removes. So it would be good to figure this out so we can detect it and say "you should run strip".

Strip also removes a bunch of debug sections. I suspect that even if we handled the anonymous trailing data described above, these debug sections might still be something of a problem, because strip may not be able to remove a section from the middle of a file while keeping a later section. (OTOH maybe it can, who knows.)

Also need to check how this works for MSVC-generated binaries and their version of stripping.

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