Re: [ECOS] Debugging information in *.S files

["Rosimildo daSilva" <rosimildo at hotmail dot com>]

>From: Jonathan Larmour <jlarmour@redhat.co.uk>
>To: Rosimildo daSilva <rosimildo@hotmail.com>
>CC: ecos-discuss@sourceware.cygnus.com
>Subject: Re: [ECOS] Debugging information in *.S files
>Date: Fri, 19 May 2000 00:04:37 +0100
> >
> > 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?
>

Jonathan,

I'd like to see the usual stuff that you need to debug a
module, such as filename, and line numbers associated with
a particular symbol. Basically, be able to set breakpoints
and step through the code with GDB, even if in one hand-written
assembly module.

Thanks for your help.

Rosimildo.









________________________________________________________________________
Get Your Private, Free E-mail from MSN Hotmail at http://www.hotmail.com