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.

Sign up for GitHub

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

Jump to bottom

.obj file in Windows does not match .hex file #5

Closed
PaperFanz opened this issue Oct 15, 2019 · 1 comment
Closed

.obj file in Windows does not match .hex file #5

PaperFanz opened this issue Oct 15, 2019 · 1 comment

Comments

@PaperFanz
Copy link
Owner

Whenever a 0x0A is written into an object file on windows, a 0x0D is inserted before it, throwing off the entire program.

Hexdumps of the Linux and Windows assemblers:
linux.txt
windows.txt

Diff:
diff.txt
PaperFanz added a commit that referenced this issue Oct 15, 2019
@PaperFanz
fix extra 0x0D byte from #5
db33b9a
@PaperFanz
Copy link
Owner Author

This issue has been resolved by opening the object file in binary mode for writing, so that no 0x0D is automatically inserted by Windows.

PaperFanz added a commit that referenced this issue Oct 15, 2019
@PaperFanz
Merge pull request #6 from PaperFanz/testing
7ad4f58 
fix extra 0x0D byte from #5
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@PaperFanz