From: Eli Zaretskii <eliz@gnu.org>
To: Nathan Sidwell <nathan@codesourcery.com>
Cc: drow@false.org, gdb-patches@sourceware.org
Subject: Re: patch for invalid hw breakpoints
Date: Fri, 02 Jun 2006 08:13:00 -0000 [thread overview]
Message-ID: <ubqtcdlg3.fsf@gnu.org> (raw)
In-Reply-To: <447FE807.6030808@codesourcery.com> (message from Nathan Sidwell on Fri, 02 Jun 2006 08:25:59 +0100)
> Date: Fri, 02 Jun 2006 08:25:59 +0100
> From: Nathan Sidwell <nathan@codesourcery.com>
> CC: Eli Zaretskii <eliz@gnu.org>, gdb-patches@sourceware.org
>
> I suspect that there's actually another failure mode which my patch fixes and it
> would be hard for remote.c to fix, and that is when the watched expression
> inserts more than one hardware watchpoint. The current code will attempt to
> insert multiple hw watchpoints, and remote.c will signal an internal error on
> inserting the second one
>
> -> Z2,11110000
> <- [empty: I don't support that.]
> tries to send: -> Z2,abcdef
> [internal error, I already know I don't support that!]
One more reason not to throw an internal error in remote.c, if you ask
me. Low-level interfaces have no business doing such things, IMHO.
next prev parent reply other threads:[~2006-06-02 8:13 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
2006-06-02 7:26 ` Nathan Sidwell
2006-06-02 8:13 ` Eli Zaretskii [this message]
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=ubqtcdlg3.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=drow@false.org \
--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