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: Tue, 19 Oct 2004 04:39:00 -0000 [thread overview]
Message-ID: <01c4b595$Blat.v2.2.2$2312b680@zahav.net.il> (raw)
In-Reply-To: <417423FA.nailP2L12S6AW@mindspring.com> (message from Michael Chastain on Mon, 18 Oct 2004 16:13:46 -0400)
> Date: Mon, 18 Oct 2004 16:13:46 -0400
> From: Michael Chastain <mec.gnu@mindspring.com>
> Cc: gdb-patches@sources.redhat.com
>
> It's like this. When gdb and gcc don't work together, I have to decide
> whether I think it's a bug in gdb (so I file a gdb PR) or a bug in gcc
> (so I file a gcc PR). Some contemplation of this relationship leads
> me to say: gdb and gcc are truly separate entities. It's not that
> "gdb X works with gcc Y", it's more exactly "gdb X and gcc Y both
> support standards Z1, Z2, and Z3".
IMHO, these considerations don't matter when a NEWS entry is being
considered. What matters then is that something which didn't work
before works now.
> eli> GDB can now debug programs compiled with the -feliminate-dwarf2-dups
> eli> option to GCC 3.3.4 or later, as well as programs compiled with
> eli> proprietary compilers that produce similar debug information (a more
> eli> compact representation of DWARF-2 debug information using the
> eli> DW_FORM_ref_addr references).
>
> Well, after fooling with this a little bit, I like my version better.
> I'm comfortable claiming that GDB supports DW_FORM_ref_addr, so that if
> a compiler produces this information, GDB can support it. I'm not
> comfortable claiming that GDB can support "programs compiled with
> proprietary compilers that produce similar debug information".
I won't start a dispute out of a 5-liner, so go ahead and commit your
version. However, at the very least replace "commercial" with
"proprietary". This is a distinction the FSF asks us to make (there's
nothing to prevent a free software project from going commercial as
long at is stays GPL-compliant).
next prev parent reply other threads:[~2004-10-19 4:39 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 [this message]
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='01c4b595$Blat.v2.2.2$2312b680@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