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

objdump return code regression #53

Closed
bmwiedemann opened this issue Jun 19, 2022 · 2 comments
Closed

objdump return code regression #53

bmwiedemann opened this issue Jun 19, 2022 · 2 comments

Comments

@bmwiedemann
Copy link
Member

bmwiedemann commented Jun 19, 2022

I noticed that 15-SP4's grub was reported as having 2 identical builds when there was plenty relevant objdump output.

git bisect pointed to

38e7800e76be477b222ff85d368c12fb179183dc is the first bad commit
commit 38e7800e76be477b222ff85d368c12fb179183dc
Author: Olaf Hering <olaf@aepfle>
Date:   Sun Mar 6 12:15:16 2022 +0100

    fix ELF comparision to really show disasm output

    Also be more specific about the old/new path.

    Fixes commit e4c745cbb083481a67e852e95f5dd93ff94a82fa

that screwed up the return code.

@bmwiedemann
Copy link
Member Author

Turther testing showed that it is the first elfdiff= that breaks the return code.

@olafhering
Copy link
Contributor

Do you have a test case?
elfdiff seems to be indicate failure in all cases.
Tthe variable objdump_failed could be removed, as it indicates some failure in the same way as elfdiff.

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

2 participants