Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: Nathan Sidwell <nathan@codesourcery.com>
Cc: gdb-patches@sourceware.org, dan@codesourcery.com
Subject: Re: patch for invalid hw breakpoints
Date: Mon, 05 Jun 2006 19:58:00 -0000	[thread overview]
Message-ID: <uodx7z88t.fsf@gnu.org> (raw)
In-Reply-To: <44843FD6.7060300@codesourcery.com> (message from Nathan Sidwell 	on Mon, 05 Jun 2006 15:29:42 +0100)

> Date: Mon, 05 Jun 2006 15:29:42 +0100
> From: Nathan Sidwell <nathan@codesourcery.com>
> CC:  gdb-patches@sourceware.org, Daniel Jacobowitz <dan@codesourcery.com>
> 
> Eli Zaretskii wrote:
> >>Date: Thu, 1 Jun 2006 17:11:59 -0400
> >>From: Daniel Jacobowitz <drow@false.org>
> >>Cc: Nathan Sidwell <nathan@codesourcery.com>, gdb-patches@sourceware.org
> >>
> 
> > 
> > Indeed.  But I think remote.c shouldn't throw an internal error in
> > such cases.
> 
> This patch ok?

Yes, thanks.


  reply	other threads:[~2006-06-05 19:58 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <447EE9A8.4050800@codesourcery.com>
2006-06-01 17:21 ` Eli Zaretskii
2006-06-01 17:26   ` Daniel Jacobowitz
2006-06-01 17:46     ` Nathan Sidwell
2006-06-01 18:03       ` Daniel Jacobowitz
2006-06-01 20:53         ` Eli Zaretskii
2006-06-01 21:12           ` Daniel Jacobowitz
2006-06-02  8:44             ` Eli Zaretskii
2006-06-02 13:52               ` Daniel Jacobowitz
2006-06-02 20:56                 ` Eli Zaretskii
2006-06-02 20:57                   ` Daniel Jacobowitz
2006-06-05 14:30               ` Nathan Sidwell
2006-06-05 19:58                 ` Eli Zaretskii [this message]
2006-06-02  7:26         ` Nathan Sidwell
2006-06-02  8:13           ` Eli Zaretskii
2006-06-01 18:33       ` Nathan Sidwell

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=uodx7z88t.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=dan@codesourcery.com \
    --cc=gdb-patches@sourceware.org \
    --cc=nathan@codesourcery.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