#105 (all objfmt/macho tests fail) – The Yasm Modular Assembler Project
Modify ↓

Ticket #105 (closed defect: fixed)

Opened 3 years ago

Last modified 3 years ago

all objfmt/macho tests fail

Reported by: mikko.tiihonen@… Owned by:
Priority: P2 Milestone:
Component: Object Format: macho Version: 0.6.0
Severity: normal Keywords:
Cc:

Description

linux, x86-64, gcc 4.1.2, CFLAGS=-O1

Test macho_test: O +0-1/1 0%

O: gas-macho32 did not match object file!

FAIL: modules/objfmts/macho/tests/gas32/gas_macho32_test.sh

Test macho_test: O +0-1/1 0%

O: gas-macho64 did not match object file!

FAIL: modules/objfmts/macho/tests/gas64/gas_macho64_test.sh

Test macho_test: OO +0-2/2 0%

O: macho-reloc did not match object file! O: machotest did not match object file!

FAIL: modules/objfmts/macho/tests/nasm32/macho32_test.sh

Test macho_test: .O +1-1/2 50%

O: machotest64 did not match object file!

FAIL: modules/objfmts/macho/tests/nasm64/macho64_test.sh

All the failures have exactly the same differenes, just at different location. Would that point to a problem when generating non-code parts, for example section headers?

Attachments

macho-diffs Download (1.7 KB) - added by mikko.tiihonen@… 3 years ago.
Differences of generated and correct macho object files

Change History

Changed 3 years ago by mikko.tiihonen@…

Differences of generated and correct macho object files

comment:1 Changed 3 years ago by peter@…

  • Status changed from new to closed
  • Resolution set to fixed

Known harmless bug, fixed in [1811] and merged to 0.6.x branch in [1818]. The differences are in unused portions of the section and segment names. The fix will be included in a future 0.6.1 release.

View ↑

Add a comment

Modify Ticket

Action
as closed
The resolution will be deleted. Next status will be 'reopened'
Author


E-mail address and user name can be saved in the Preferences.

Attachments ↑
 
Note: See TracTickets for help on using tickets.