Mirror of the gdb mailing list
 help / color / mirror / Atom feed
From: Stan Shebs <shebs@apple.com>
To: Andrew Cagney <ac131313@redhat.com>
Cc: Eli Zaretskii <eliz@elta.co.il>, gdb@sources.redhat.com
Subject: Re: Features vs infrastructure (was Re: Tracepoint support in Cygnus GDB ?)
Date: Thu, 02 Oct 2003 06:04:00 -0000	[thread overview]
Message-ID: <3F7BC005.9050707@apple.com> (raw)
In-Reply-To: <3F7B9B85.50201@redhat.com>

Andrew Cagney wrote:

>> I just thumbed through the GDB website and sources, and gdb/TODO seemed
>> like it was mostly a list of desired infrastructure changes.  For 
>> instance,
>> I didn't see a mention of the desirability of tracepoint support for 
>> native
>> debugging, although that is an obvious item for a wishlist.  Perhaps the
>> todo list should be separated into "user-visible" and "infrastructure"
>> sections, with appropriate xrefs, so that everybody is aware of what's
>> desired.
>
>
> GDB tracks new features using the bug database.  I see one tracepoint 
> change which is me pointing out that an architecture method is broken. 
> Must remember to delete the TODO file.

OK, I see plenty there, but most look like infrastructure changes,
and of the 139 items, I still can't tell which are the most
important features that users have been waiting for.  That's
where a real document comes in handy; you can use it to explain
why features A, B, and C are more important than D, E, and F,
or why feature G must wait for infrastructure changes H, I, and J.

Stan



  parent reply	other threads:[~2003-10-02  6:04 UTC|newest]

Thread overview: 30+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-09-24 10:40 Tracepoint support in Cygnus GDB ? Saravanan
2003-09-24 18:12 ` Eli Zaretskii
2003-09-24 22:41   ` Jim Blandy
2003-09-25  4:02     ` Daniel Jacobowitz
2003-09-25 21:44     ` Andrew Cagney
2003-09-27 15:46       ` Eli Zaretskii
2003-09-27 17:49         ` Andrew Cagney
2003-09-27 18:37           ` Eli Zaretskii
2003-09-27 18:48             ` Andrew Cagney
2003-09-28  8:40               ` Eli Zaretskii
2003-09-28 19:44                 ` Andrew Cagney
2003-09-28 21:07                   ` Eli Zaretskii
2003-09-28 21:30                     ` Daniel Jacobowitz
2003-09-29  5:36                       ` Eli Zaretskii
2003-09-29 14:48                         ` Daniel Jacobowitz
2003-09-28 22:25                     ` Andrew Cagney
2003-09-29  5:41                       ` Eli Zaretskii
2003-09-29 14:52                         ` Andrew Cagney
2003-09-29 15:07                           ` Daniel Jacobowitz
2003-10-01 21:49                           ` Features vs infrastructure (was Re: Tracepoint support in Cygnus GDB ?) Stan Shebs
2003-10-02  3:29                             ` Andrew Cagney
2003-10-02  3:47                               ` Stan Shebs
2003-10-02  5:31                                 ` Andrew Cagney
2003-10-02  6:42                                   ` Stan Shebs
2003-10-02  7:02                                     ` Joel Brobecker
2003-10-02 19:18                                       ` Andrew Cagney
2003-10-02  6:04                               ` Stan Shebs [this message]
2003-10-02  6:29                                 ` Andrew Cagney
2003-09-30  5:43           ` Tracepoint support in Cygnus GDB ? Jim Blandy
2003-09-30 21:14             ` 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=3F7BC005.9050707@apple.com \
    --to=shebs@apple.com \
    --cc=ac131313@redhat.com \
    --cc=eliz@elta.co.il \
    --cc=gdb@sources.redhat.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