From mboxrd@z Thu Jan 1 00:00:00 1970 From: Andrew Cagney To: Orjan Friberg Cc: gdb-patches@sources.redhat.com Subject: Re: Z packet support in Gdbserver? Date: Wed, 26 May 2004 17:32:00 -0000 Message-id: <40B4D494.9020504@gnu.org> References: <40B3650C.5090800@axis.com> <40B38A5F.8050001@gnu.org> <40B47B2B.8020504@axis.com> X-SW-Source: 2004-05/msg00752.html 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