Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: "Eli Zaretskii" <eliz@gnu.org>
To: Daniel Jacobowitz <dan@debian.org>
Cc: mec.gnu@mindspring.com, gdb-patches@sources.redhat.com
Subject: Re: [rfc/NEWS] GDB works with GCC -feliminate-dwarf2-dups.
Date: Sun, 17 Oct 2004 19:45:00 -0000	[thread overview]
Message-ID: <01c4b481$Blat.v2.2.2$7466ede0@zahav.net.il> (raw)
In-Reply-To: <20041017183143.GA22628@nevyn.them.org> (message from Daniel Jacobowitz on Sun, 17 Oct 2004 14:31:44 -0400)

> Date: Sun, 17 Oct 2004 14:31:44 -0400
> From: Daniel Jacobowitz <dan@debian.org>
> Cc: eliz@gnu.org, gdb-patches@sources.redhat.com
> 
>  GDB now supports a more compact representation of DWARF-2 debug
>  information using DW_FORM_ref_addr references.  These are produced by
>  some commercial compilers, and by GCC's -feliminate-dwarf2-dups
>  option.  You must use GCC 3.3.4 or later to use this option.
> 
> How's that?

I liked Michael's original version better: it is more user-oriented.

If it is important to mention technicalities like DW_FORM_ref_addr,
then I think they should come _after_ Michael's user-oriented
description.


  parent reply	other threads:[~2004-10-17 19:45 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-10-17 18:12 Michael Chastain
2004-10-17 18:31 ` Daniel Jacobowitz
2004-10-17 18:53   ` Michael Chastain
2004-10-17 19:13     ` Daniel Jacobowitz
2004-10-17 20:11       ` Michael Chastain
2004-10-18  5:01         ` Eli Zaretskii
2004-10-18 20:14           ` Michael Chastain
2004-10-19  4:39             ` Eli Zaretskii
2004-10-19 13:23               ` Daniel Jacobowitz
2004-10-19 20:05                 ` Eli Zaretskii
2004-10-19 19:37               ` Michael Chastain
2004-10-17 19:45   ` Eli Zaretskii [this message]
2004-10-17 19:42 ` Eli Zaretskii

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='01c4b481$Blat.v2.2.2$7466ede0@zahav.net.il' \
    --to=eliz@gnu.org \
    --cc=dan@debian.org \
    --cc=gdb-patches@sources.redhat.com \
    --cc=mec.gnu@mindspring.com \
    /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