From mboxrd@z Thu Jan  1 00:00:00 1970
From: Grant Edwards <grante@visi.com>
To: Jonathan Larmour <jlarmour@redhat.com>
Cc: "Trenton D. Adams" <tadams@extremeeng.com>, 'eCos Discussion' <ecos-discuss@sourceware.cygnus.com>
Subject: Re: [ECOS] objdump for binary file
Date: Tue, 21 Aug 2001 13:22:00 -0000
Message-id: <20010821152426.A1261@visi.com>
References: <000001c12a76$be9926a0$090110ac@TRENT> <20010821143446.A922@visi.com> <3B82BE3D.B73122BC@redhat.com>
X-SW-Source: 2001-08/msg00713.html

On Tue, Aug 21, 2001 at 09:02:05PM +0100, Jonathan Larmour wrote:
> Grant Edwards wrote:
> > 
> > On Tue, Aug 21, 2001 at 01:23:22PM -0600, Trenton D. Adams wrote:
> > 
> > > I compiled an eCos program and then copied it to a binary file.  Is
> > > there a way of dumping the assembly now?
> > 
> > No.
> 
> Yes :-). It's not pretty and you've lost all the symbol info, but you can
> disassemble everything (including data!). e.g.
> 
> echo > foo.c
> arm-elf-gcc -c -o foo.o foo.c
> arm-elf-objcopy --remove-section=.text foo.o
> arm-elf-objcopy --add-section=.text=thebinfile foo.o
> arm-elf-objcopy --set-section-flags=.text=alloc,load,code,contents,readonly foo.o
> arm-elf-objdump -d foo.o

The bit at the top where you compile an empty C file to
generate all the right sections is clever -- I hadn't thought
of that.

One would hope he kept a copy of the ELF file -- or can
re-generate it.  Making sense of a binary file by disassembling
it requires considerable skill and can use up lots of hours for
a non-trivial program.

-- 
Grant Edwards
grante@visi.com