OpenCores
Issue List
objdump does not create correct machine #144
Closed wallento opened this issue over 13 years ago
wallento commented over 13 years ago

When doing an "objdump -I binary -O elf32-or32", the resulting object file cannot be linked with gcc, because of a wrong machine code in the header. I observed, that byte 19 is different, namely 0x00 instead of 0x5c.

Bye, Stefan

PS: Temporarely, running this python script solves it: import mmap from sys import argv

if (len(argv) == 1): print "Provide file to patch as parameter" exit(1)

f = open(argv1,"r+b") map = mmap.mmap(f.fileno(),20) map19 = '\x5c' map.close()

wallento commented over 13 years ago

Type your text here

jeremybennett commented over 13 years ago

Hi Stefan,

Thanks for the bug report. There's a lot of stuff in binutils that is doubtful. Up until the most recent fixes it wasn't even linking stuff as ELF (it used generic rather than ELF internally).

jeremybennett commented almost 13 years ago
<p> Transferred to OpenRISC bugzilla (<a href="http://bugzilla.opencores.org/show_bug.cgi?id=31">Bug 31</a>). </p> <p> Marking closed in this bugtracker. </p>
jeremybennett was assigned almost 13 years ago
jeremybennett closed this almost 13 years ago

Assignee
jeremybennett
Labels
Bug