From: Orjan Friberg <orjan.friberg@axis.com>
To: Daniel Jacobowitz <drow@false.org>
Cc: gdb-patches@sources.redhat.com
Subject: Re: Z packet support in Gdbserver?
Date: Wed, 26 May 2004 08:05:00 -0000 [thread overview]
Message-ID: <40B44FC0.1070005@axis.com> (raw)
In-Reply-To: <20040525152659.GA22274@nevyn.them.org>
Daniel Jacobowitz wrote:
It's much simpler than that: gdbserver does not support hardware
watchpoints. No one's ever implemented it. As a copy/paste exercise
it would not be too hard; I still have pipe dreams of sharing the code
with GDB someday.
Ah, that explains it. So what's needed is basically two new function
pointers in struct target_ops (insert_watchpoint/remove_watchpoint) and
a snippet of code in server.c to recognize the z/Z packets. (I assume
that's what you meant by copy/paste exercise.)
--
Orjan Friberg
Axis Communications
next prev parent reply other threads:[~2004-05-26 8:05 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <40B3650C.5090800@axis.com>
2004-05-25 15:27 ` Daniel Jacobowitz
2004-05-26 8:05 ` Orjan Friberg [this message]
2004-05-25 18:03 ` Andrew Cagney
2004-05-26 11:10 ` Orjan Friberg
2004-05-26 17:32 ` 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=40B44FC0.1070005@axis.com \
--to=orjan.friberg@axis.com \
--cc=drow@false.org \
--cc=gdb-patches@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