From: Daniel Jacobowitz <drow@mvista.com>
To: Eli Zaretskii <eliz@is.elta.co.il>
Cc: James Sampson <i_am_triumph@ofir.dk>,
Andrew Cagney <ac131313@redhat.com>,
GDB Archive <gdb@sources.redhat.com>
Subject: Re: Porting GDB - Where to start?
Date: Mon, 02 Dec 2002 06:28:00 -0000 [thread overview]
Message-ID: <20021202142903.GA7113@nevyn.them.org> (raw)
In-Reply-To: <Pine.SUN.3.91.1021202081514.29205J-100000@is>
On Mon, Dec 02, 2002 at 08:16:17AM +0200, Eli Zaretskii wrote:
>
> On Sun, 1 Dec 2002, Daniel Jacobowitz wrote:
>
> > > In CCS you have the option to use COFF or DWARF. I was planning on using COFF,
> > > because I have noticed some C54x COFF file thingies in the BFD, which could be
> > > usable :-D. Do you know if they are?.
> >
> > If those are the two switches that's pretty bizarre. COFF is a file
> > format, DWARF a debug info format.
>
> Not 100% accurate, AFAIK: there's also COFF debug info format.
>
> > You probably want DWARF (DWARF-2) which implies ELF format files.
>
> DWARF-2 is also supported with COFF binary format. DJGPP uses that
> combination.
Really? How does that work? I recall a number of blatant ELFisms in
dwarf2, both specification and implementation. I suppose that if COFF
has arbitrary named sections, it could work - but I thought only ECOFF
did that.
--
Daniel Jacobowitz
MontaVista Software Debian GNU/Linux Developer
next prev parent reply other threads:[~2002-12-02 14:28 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-11-26 7:53 James Sampson
2002-12-01 13:18 ` Daniel Jacobowitz
2002-12-01 22:16 ` Eli Zaretskii
2002-12-02 6:28 ` Daniel Jacobowitz [this message]
2002-12-02 11:14 ` Eli Zaretskii
-- strict thread matches above, loose matches on Subject: below --
2002-11-26 0:15 James Sampson
2002-11-26 7:01 ` Andrew Cagney
2002-12-03 22:48 ` Jim Blandy
2002-11-25 1:56 James Sampson
2002-11-25 6:29 ` Daniel Jacobowitz
2002-11-25 10:22 ` Andrew Cagney
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20021202142903.GA7113@nevyn.them.org \
--to=drow@mvista.com \
--cc=ac131313@redhat.com \
--cc=eliz@is.elta.co.il \
--cc=gdb@sources.redhat.com \
--cc=i_am_triumph@ofir.dk \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox