From: Wu Zhou <woodzltc@cn.ibm.com>
To: Daniel Jacobowitz <drow@false.org>
Cc: gdb@sources.redhat.com
Subject: Re: Some questions w.r.t remote watchpoint support in i386
Date: Mon, 22 May 2006 16:39:00 -0000 [thread overview]
Message-ID: <Pine.LNX.4.64.0605212157111.7830@localhost.localdomain> (raw)
In-Reply-To: <20060425125422.GB21293@nevyn.them.org>
> > 1. The first error I encounter is: "Couldn't write debug register: No such
> > process".
> >
> > After some tracking, I found gdb client is calling target_insert_watchpoint
> > defined in config/i386/nm-i386.h, instead of the remote_insert_watchpoint
> > defined in remote.c
> >
> > I guess this is a more general problem. Whenever you change target under
> > i386 platform, you will always get the i386_insert_watchpoint (and other
> > three target operations) executed.
> >
> > Maybe we can put these target operation into the target_ops, instead of
> > defining them as macro in config/i386/nm-i386.h?
>
> Yes, someone needs to fix this.
I had a closer look at this. It seems this will involve quite a few gdb
configs. Almost all the native header files in config/i386 include
nm-i386.h, but their responsive native c source are very different. To
delete these macros in nm-i386.h, I believe we need to put their
counterpart target vectore into all these responsive native c source.
And we also need to test that all relevant configs are ok after the
changes. It seems hard to me. Anyone have any good idea?
>
> > 2. Following the above thought, I comment out these four macros in
> > config/i386/nm-i386.h, and add them into i386-linux-nat.c
> >
> > This time, local gdb will call remote_insert_watchpoint indeed, but I get
> > another error:
> >
> > Can't clear hardware watchpoints without the 'Z2' (write-watchpoint) packet.
> >
> > "set debug remote 1" tell me that Packet Z2 (write-watchpoint) is NOT
> > supported
> >
> > I tried to use "set remote write-watchpoint-packet 1", but it won't work
> > either:
> >
> > Enabled packet Z2 (write-watchpoint) not recognized by stub
> >
> > my question here is:
> >
> > What is the stub refered to here? Is it the gdbserver? And how can
> > gdbserver determine which packat he will support, which won't?
>
> The stub is gdbserver, yes. It supports what it supports, and does not
> support what no one has implemented! And no one has implemented i386
> watchpoints for gdbserver.
It seems that there is not many requirement for this? Maybe i386 is not a
very popular gdbserver platform. :-)
Regards
- Wu Zhou
prev parent reply other threads:[~2006-05-21 14:14 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-04-25 12:54 Wu Zhou
2006-04-25 19:34 ` Daniel Jacobowitz
2006-05-22 16:39 ` Wu Zhou [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=Pine.LNX.4.64.0605212157111.7830@localhost.localdomain \
--to=woodzltc@cn.ibm.com \
--cc=drow@false.org \
--cc=gdb@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