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

[BUG] x86 scratches can have errors due to problematic data being included by objdump #1192

Open
1superchip opened this issue Apr 5, 2024 · 0 comments
Labels
backend bug Unintended behaviour

Comments

@1superchip
Copy link
Contributor

Some scratches do not work due to extra data objdump emits in its output.
The compiler can generate extra functions/data in a .text$x section which is dumped by objdump if "-j .text" isn't passed.

Error shown in the scratch:
"Diff error: Error running asm-differ: failed to find address immediate for line 'add %al,(%eax)'"
This error is from asm-differ attempting to process incorrect data which is included in the objdump output.

Expected behavior
The problematic data should not be included in the objdump output by passing "-j .text".

Scratches
https://decomp.me/scratch/x0FQW

Additional context
i686-w64-mingw32-objdump dumps .text and .text$x when it is not passed a section to dump with the -j option.
objdump does not dump .text$x when passed "-j .text".

@bates64 bates64 added bug Unintended behaviour backend labels Apr 25, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
backend bug Unintended behaviour
Projects
None yet
Development

No branches or pull requests

2 participants