This is the mail archive of the
ecos-discuss@sourceware.cygnus.com
mailing list for the eCos project.
Re: Debugging information in *.S files
- To: Rosimildo daSilva <rosimildo at hotmail dot com>
- Subject: Re: [ECOS] Debugging information in *.S files
- From: Jonathan Larmour <jlarmour at redhat dot co dot uk>
- Date: Fri, 19 May 2000 00:04:37 +0100
- CC: ecos-discuss at sourceware dot cygnus dot com
- Organization: Red Hat UK Ltd.
- References: <20000518034414.6706.qmail@hotmail.com>
Rosimildo daSilva wrote:
>
> >From: Jonathan Larmour <jlarmour@redhat.co.uk>
> >
> >Well, debug information is contained in the .s assembler files that gcc
> >generates with -g if that's what you mean.
> >
>
> Yes, this is exactly what I meant.
> I have doubled checked one more time, and it does not work for me.
>
> Below you have the results of compiling vectors.S:
>
> --------------------------------------------------------------------
> make[1]: Entering directory `/ecos/stubs/hal/mips/arch/v1_3_1'
> mips-r3041-elf-gcc -Wp,-MD,vectors.tmp -I/ecos/stubs/install/include
> -I/ecos/ec
> os-1.3.1/packages/hal/mips/arch/v1_3_1
> -I/ecos/ecos-1.3.1/packages/hal/mips/arch
> /v1_3_1/src -I/ecos/ecos-1.3.1/packages/hal/mips/arch/v1_3_1/tests -I. -EL
> -Wall
> -Wpointer-arith -Wstrict-prototypes -Winline -Wundef -Woverloaded-virtual -g
> -O
> 2 -ffunction-sections -fdata-sections -fno-rtti -fno-exceptions -fvtable-gc
> -fin
> it-priority -c -o /ecos/stubs/install/lib/vectors.o
> /ecos/ecos-1.3.1/packages/ha
> l/mips/arch/v1_3_1/src/vectors.S
> -------------------------------------------------------------
>
> bash-2.03$
> bash-2.03$ cd install/lib/
> bash-2.03$ ls
> extras.o libextras.a libtarget.a target.ld vectors.o
> bash-2.03$ mips-r3041-elf-objdump --debugging vectors.o
>
> vectors.o: file format elf32-littlemips
>
> vectors.o: no recognized debugging information
Oops, what I wrote was somewhat ambiguous: when I said about debugging
information that gcc generates, I meant when compiling C/C++ files. If you
are using gcc as a frontend to the assembler, as when compiling vectors.S,
then that's the same as the "hand-coded assembler" case I referred to in my
previous e-mail.
What debugging information would you expect to be in a hand-written
assembler file?
Jifl
--
Red Hat, 35 Cambridge Place, Cambridge, UK. CB2 1NS Tel: +44 (1223) 728762
"Plan to be spontaneous tomorrow." || These opinions are all my own fault