Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Andrew Cagney <cagney@gnu.org>
To: Orjan Friberg <orjan.friberg@axis.com>
Cc: gdb-patches@sources.redhat.com
Subject: Re: Z packet support in Gdbserver?
Date: Wed, 26 May 2004 17:32:00 -0000	[thread overview]
Message-ID: <40B4D494.9020504@gnu.org> (raw)
In-Reply-To: <40B47B2B.8020504@axis.com>

Andrew Cagney wrote:

There are two ways to implement h/w watchpoints: in the target (as was done for remote.c); or in the per-architecture code (as was done for native i386).  Both are correct.  The missing bit is code to get the per-architecture logic working with a remote target - this would involve juggling things so that the h/w watchpoint registers are included in the regcache and the target/arch to select either a local/remote mechanism.


Ok; I think I understand.  The CRISv32 target is unlikely to ever have a native debugger, but as a remote target it will be debuggable in kernel mode (using a traditional remote stub) and in user mode (using Gdbserver).  For kernel mode, I have implemented the h/w watchpoint register setup as a response to z/Z packets, so either I have to duplicate that in the Gdbserver, or move it all into GDB, and have it done through G packets.
Yep.

Andrew




      reply	other threads:[~2004-05-26 17:32 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
2004-05-25 18:03 ` Andrew Cagney
2004-05-26 11:10   ` Orjan Friberg
2004-05-26 17:32     ` Andrew Cagney [this message]

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=40B4D494.9020504@gnu.org \
    --to=cagney@gnu.org \
    --cc=gdb-patches@sources.redhat.com \
    --cc=orjan.friberg@axis.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