From: Andrew Cagney <ac131313@ges.redhat.com>
To: Grace Sainsbury <graces@redhat.com>
Cc: gdb-patches@sources.redhat.com
Subject: Re: [rfa] hardware breakpoints -- remote targets
Date: Fri, 09 Aug 2002 09:26:00 -0000 [thread overview]
Message-ID: <3D53ED21.6090001@ges.redhat.com> (raw)
In-Reply-To: <20020809114146.A29942@tomago.toronto.redhat.com>
> I made the sugested changes, and removed the set and show functions
> from this patch.
>
> ok?
>
> grace
>
> 2002-08-09 Grace Sainsbury <graces@redhat.com>
>
> * remote.c: (remote_wait, remote_async_wait): Add check for awatch
> T-packets; the 'a' is not taken as a register number.
> (remote_check_watch_resources, remote_stopped_by_watchpoint)
> (remote_stopped_data_address): New functions; add to target
> vector.
> (remote_insert_hw_breakpoint, remote_remove_hw_breakpoint): Change
> prototypes to match other implementations of this
> function. replace integer argument with pointer -- the length
> field in the Z-packet is the length of what is pointed to or 1 if
> pointer is null. Add to target vector.
> (remote_insert_watchpoint, remote_remove_watchpoint): Add to
> target vector.
>
Yes. Thanks!
I suspect the set/show stuff is going to need a bit of brainstorming
(and knowing GDB's luck, a refinement to the remote protocol).
Hmm, now you get to the tricky bit. Getting a single native
i386-unknown-linux-gnu gdb to use remote watchpoints when remote but
native watchpoints when native ... :-)
enjoy,
Andrew
next prev parent reply other threads:[~2002-08-09 16:26 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-08-06 9:19 Grace Sainsbury
2002-08-08 10:06 ` Grace Sainsbury
2002-08-08 11:30 ` Andrew Cagney
2002-08-08 12:44 ` [patch] remote.c: unpack_varlen_hex Grace Sainsbury
2002-08-09 8:41 ` [rfa] hardware breakpoints -- remote targets Grace Sainsbury
2002-08-09 9:26 ` Andrew Cagney [this message]
2002-08-11 6:48 ` Eli Zaretskii
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=3D53ED21.6090001@ges.redhat.com \
--to=ac131313@ges.redhat.com \
--cc=gdb-patches@sources.redhat.com \
--cc=graces@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