Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Andrew Cagney <ac131313@redhat.com>
To: Daniel Jacobowitz <drow@mvista.com>
Cc: Michael Elizabeth Chastain <mec@shout.net>,
	fnasser@redhat.com, gdb-patches@sources.redhat.com
Subject: Re: [rfa] new test, pr-1090.exp, multi-register variables
Date: Mon, 24 Feb 2003 15:37:00 -0000	[thread overview]
Message-ID: <3E5A3CC5.3080700@redhat.com> (raw)
In-Reply-To: <20030224142146.GA24769@nevyn.them.org>

> On Mon, Feb 24, 2003 at 02:29:29AM -0500, Andrew Cagney wrote:
> 
>> Just FYI,
>> 
> 
>> >To my mind, these are critical bugs, because gdb quietly prints the
>> >wrong information.  If we can't fix it for 5.4/6.0 then I want to
>> >add gdb/214 and gdb/1090 to the PROBLEMS file.
> 
>> 
>> The only critical thing in GDB 5.4/6.0 is ensuring that the new EMACS 
>> mode has everything it needs without relying on level two annotiations. 
>>  And that has a very hard deadline :-(
> 
> 
> I beg to differ.  Why should Emacs dictate our schedule?  Why shouldn't
> critical debugging issues?

Did you read the thread on gdb@?

GDB is a member of the GNU project and as such, it is expected to 
balance its own objectives against those of the larger GNU community.

If GDB doesn't fix a debugging problem in this release, it can can be 
fixed in the next release.

However, if GDB doesn't get the MI working quick smart, GDB maintainaers 
(i.e., you) will be stuck maintaining annotation level two from now 
until eternity.

Andrew



  reply	other threads:[~2003-02-24 15:37 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-02-24  4:35 Michael Elizabeth Chastain
2003-02-24  5:06 ` Daniel Jacobowitz
2003-02-24  7:27 ` Andrew Cagney
2003-02-24 14:21   ` Daniel Jacobowitz
2003-02-24 15:37     ` Andrew Cagney [this message]
  -- strict thread matches above, loose matches on Subject: below --
2003-02-24 15:06 Michael Elizabeth Chastain
2003-02-24  3:55 Michael Elizabeth Chastain
2003-02-24  4:17 ` Daniel Jacobowitz
2003-02-24  7:07   ` Daniel Berlin

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=3E5A3CC5.3080700@redhat.com \
    --to=ac131313@redhat.com \
    --cc=drow@mvista.com \
    --cc=fnasser@redhat.com \
    --cc=gdb-patches@sources.redhat.com \
    --cc=mec@shout.net \
    /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