public inbox for gdb@sourceware.org
 help / color / mirror / Atom feed
From: Andrew Cagney <ac131313@redhat.com>
To: Tim Combs <tcombs@urbana.css.mot.com>
Cc: Michael Elizabeth Chastain <mec@shout.net>,
	dberlin@dberlin.org, gdb@sources.redhat.com
Subject: Re: Deprecate dwarf and mdebug support, delete nlm?
Date: Mon, 05 May 2003 17:30:00 -0000	[thread overview]
Message-ID: <3EB69FCA.70409@redhat.com> (raw)
In-Reply-To: <20030505102345.B11039@urbana.css.mot.com>

> I don't think its a fair measure to equate number of  patches with value.

The number of patches does at least hint at the level of activity.  As 
for value, part of a value judgment is determining the cost.

> I've still got users who are using commercial compilers that emit dwarf1 and
> it would be a great loss to these users if dwarf1 went away.

Significant structural change, such as adding support for multiple 
address spaces, moves more rapidly when there are fewer debug readers to 
content with.  These users potential loss is someone elses potential 
gain.  These users can also continue to use an existing GDB.

As someone (michael?) suggested, can these users move to Free compilers?

>> Here is the URL for one guy who has a diab compiler and wanted
>> to improve gdb dwarf-1 support:
>> 
>>   http://sources.redhat.com/ml/gdb-patches/2002-07/msg00505.html
>> 
>> That's the extent of interest in dwarf-1: two people in the past year
>> with diab compiler: this guy, and one other that I didn't dig up
>> the URL for yet.

Andrew

  reply	other threads:[~2003-05-05 17:30 UTC|newest]

Thread overview: 28+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-05-04 16:08 Michael Elizabeth Chastain
2003-05-05 15:23 ` Tim Combs
2003-05-05 17:30   ` Andrew Cagney [this message]
2003-05-05 17:49     ` Daniel Berlin
  -- strict thread matches above, loose matches on Subject: below --
2003-05-09 15:47 Michael Elizabeth Chastain
2003-05-09 16:37 ` Kean Johnston
2003-05-09 17:03   ` Andrew Cagney
2003-05-09 16:48 ` Andrew Cagney
2003-05-10  9:25   ` Eli Zaretskii
2003-05-09 15:22 Michael Elizabeth Chastain
2003-05-09 15:34 ` Kean Johnston
2003-05-09  8:10 Armin Diehl
     [not found] <200305082242.h48MgQH06975@mx1.redhat.com>
2003-05-09  0:02 ` Elena Zannoni
     [not found] <E19Duaa-0005kw-00@monty-python.gnu.org>
2003-05-08 23:42 ` Andrew Cagney
2003-05-09 15:12   ` Kean Johnston
2003-05-08 23:14 Günter Knauf
2003-05-08 22:52 Ulrich Neumann
2003-05-09  0:09 ` Elena Zannoni
2003-05-08 22:42 Günter Knauf
2003-05-04  6:10 Michael Elizabeth Chastain
2003-05-04  6:43 ` Daniel Berlin
2003-05-04  4:41 Andrew Cagney
2003-05-04 15:41 ` Daniel Jacobowitz
2003-05-04 19:52 ` Elena Zannoni
2003-05-05 17:37   ` Andrew Cagney
2003-05-05  0:14 ` Andrew Cagney
2003-05-05  3:58 ` Joel Brobecker
2003-05-05 17:24 ` Jim Blandy

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=3EB69FCA.70409@redhat.com \
    --to=ac131313@redhat.com \
    --cc=dberlin@dberlin.org \
    --cc=gdb@sources.redhat.com \
    --cc=mec@shout.net \
    --cc=tcombs@urbana.css.mot.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).