Mirror of the gdb mailing list
 help / color / mirror / Atom feed
From: "Eli Zaretskii" <eliz@is.elta.co.il>
To: drow@mvista.com
Cc: i_am_triumph@ofir.dk, ac131313@redhat.com, gdb@sources.redhat.com
Subject: Re: Porting GDB - Where to start?
Date: Mon, 02 Dec 2002 11:14:00 -0000	[thread overview]
Message-ID: <3405-Mon02Dec2002211309+0200-eliz@is.elta.co.il> (raw)
In-Reply-To: <20021202142903.GA7113@nevyn.them.org> (message from Daniel Jacobowitz on Mon, 2 Dec 2002 09:29:03 -0500)

> Date: Mon, 2 Dec 2002 09:29:03 -0500
> From: Daniel Jacobowitz <drow@mvista.com>
> > 
> > DWARF-2 is also supported with COFF binary format.  DJGPP uses that 
> > combination.
> 
> Really?  How does that work?

Quite frankly, I have no idea; I just know it does.  You could
probably find the details in the GCC sources, though.

> I suppose that if COFF has arbitrary named sections, it could work -
> but I thought only ECOFF did that.

FWIW, the DJGPP linker script has this snippet:

      /* DWARF 2 */
      .debug_aranges  0 : { *(.debug_aranges) }
      .debug_pubnames 0 : { *(.debug_pubnames) }
      .debug_info     0 : { *(.debug_info) *(.gnu.linkonce.wi.*) }
      .debug_abbrev   0 : { *(.debug_abbrev) }
      .debug_line     0 : { *(.debug_line) }
      .debug_frame    0 : { *(.debug_frame) }
      .debug_str      0 : { *(.debug_str) }
      .debug_loc      0 : { *(.debug_loc) }
      .debug_macinfo  0 : { *(.debug_macinfo) }


  reply	other threads:[~2002-12-02 19:14 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
2002-12-02 11:14       ` Eli Zaretskii [this message]
  -- 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=3405-Mon02Dec2002211309+0200-eliz@is.elta.co.il \
    --to=eliz@is.elta.co.il \
    --cc=ac131313@redhat.com \
    --cc=drow@mvista.com \
    --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