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 14:32:20 +0100
- CC: ecos-discuss at sourceware dot cygnus dot com
- Organization: Red Hat UK Ltd.
- References: <20000519132005.71453.qmail@hotmail.com>
Rosimildo daSilva wrote:
> >What debugging information would you expect to be in a hand-written
> >assembler file?
>
> 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.
Normally there isn't demand for such a thing - the generated assembly
corresponds nearly one-to-one with the assembly in the file, so stepi is
sufficient.
I did see this assembler option though:
--gstabs
Generate stabs debugging information for each assembler
line. This may help debugging assembler code, if the debugger can handle
it.
I haven't tried it though.
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