From: "Eli Zaretskii" <eliz@gnu.org>
To: Michael Chastain <mec.gnu@mindspring.com>
Cc: dan@debian.org, gdb-patches@sources.redhat.com
Subject: Re: [rfc/NEWS] GDB works with GCC -feliminate-dwarf2-dups.
Date: Mon, 18 Oct 2004 05:01:00 -0000 [thread overview]
Message-ID: <01c4b4cf$Blat.v2.2.2$1a0e6f00@zahav.net.il> (raw)
In-Reply-To: <4172D1FF.nailMO5211TI7@mindspring.com> (message from Michael Chastain on Sun, 17 Oct 2004 16:11:43 -0400)
> Date: Sun, 17 Oct 2004 16:11:43 -0400
> From: Michael Chastain <mec.gnu@mindspring.com>
> Cc: gdb-patches@sources.redhat.com
>
> Eli, I like this better than my original wording because gdb does
> not actually support versions of gcc; gdb supports certain debug
> formats, which gcc also supports.
I don't understand what you are saying; the original text was:
* GDB works with GCC -feliminate-dwarf2-dups
GDB now works with programs compiled with -feliminate-dwarf2-dups.
You must use GCC 3.3.4 or later to use this option.
Where does this say that GDB supports versions of GCC?
> So about this version?
I'd prefer something like this:
* GDB works with GCC -feliminate-dwarf2-dups
GDB can now debug programs compiled with the -feliminate-dwarf2-dups
option to GCC 3.3.4 or later, as well as programs compiled with
proprietary compilers that produce similar debug information (a more
compact representation of DWARF-2 debug information using the
DW_FORM_ref_addr references).
That is what I meant in my previous message: put the user-oriented
information first, and the technicalities after that.
next prev parent reply other threads:[~2004-10-18 5:01 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 [this message]
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
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='01c4b4cf$Blat.v2.2.2$1a0e6f00@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