Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Daniel Jacobowitz <drow@false.org>
To: Nick Roberts <nickrob@snap.net.nz>
Cc: gdb-patches@sources.redhat.com
Subject: Re: [PATCH] -data-list-changed-registers (Take 2)
Date: Fri, 17 Jun 2005 01:51:00 -0000	[thread overview]
Message-ID: <20050617015059.GC17013@nevyn.them.org> (raw)
In-Reply-To: <17070.17646.968472.157418@farnswood.snap.net.nz>

On Tue, Jun 14, 2005 at 02:46:06PM +1200, Nick Roberts wrote:
>  > > I get many failures on the testsuite, I'll try to move to a newer
>  > > PC/kernel.  mi-regs.exp seems OK though.
>  > 
>  > What failures, in particular?
> 
> I don't think you'll want to know, I think a lot of them are kernel
> related (2.4.19-16mdk).  I've attached the results below of a run with a
> newer kernel (2.6.9.1-1.667 Fedora Core 3)

These results are sane.  FYI, if you use a full path to run configure,
the mi-basics failures will go away.

> I've made more changes to gdb-mi.el now (it use -data-list-changed-registers
> now, for a start).  Since resources do seem to be stretched, and this is
> separate code that can't break GDB, could I be given authority to check in
> changes to this just this one file i.e. in MAINTAINERS:
> 
> Core: Generic components used by all of GDB
> ...
> gdb-mi.el               nickrob@snap.net.nz 
> 
> I did suggest this once to Andrew, but it never got resolved.  It might need
> an emergency general meeting and you might have to dust off a copy of the
> Constitution, but in reality its no big deal.  I've been doing something like
> this for Emacs for a couple of years now without problems.

The only reason I haven't approved the gdb-mi.el you last posted was
because it depended on the MI patch which you just reminded me to look
at (which was an interface change, and I hadn't had a chance to
digest it yet).  I do not want you to commit anything which uses MI
interfaces that don't exist yet!  Normally, I'd be perfectly willing to
rubber-stamp it in.

-- 
Daniel Jacobowitz
CodeSourcery, LLC


  reply	other threads:[~2005-06-17  1:51 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-06-01 11:12 [PATCH] -data-list-changed-registers Nick Roberts
2005-06-03 19:13 ` Daniel Jacobowitz
2005-06-03 22:35   ` Nick Roberts
2005-06-03 22:36     ` Daniel Jacobowitz
2005-06-04 11:41       ` Nick Roberts
2005-06-06 20:44         ` Nick Roberts
2005-06-11  5:54           ` Nick Roberts
2005-06-11  6:50           ` [PATCH] -data-list-changed-registers (Take 2) Nick Roberts
2005-06-13  2:40             ` Daniel Jacobowitz
2005-06-13  4:47               ` Nick Roberts
2005-06-13 13:48                 ` Daniel Jacobowitz
2005-06-13 22:38                   ` Nick Roberts
2005-06-13 22:42                     ` Daniel Jacobowitz
2005-06-14  2:45                       ` Nick Roberts
2005-06-17  1:51                         ` Daniel Jacobowitz [this message]
2005-06-17  3:13                           ` Nick Roberts
2005-06-17  3:22                             ` Daniel Jacobowitz

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=20050617015059.GC17013@nevyn.them.org \
    --to=drow@false.org \
    --cc=gdb-patches@sources.redhat.com \
    --cc=nickrob@snap.net.nz \
    /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