From: Daniel Jacobowitz <dan@codesourcery.com>
To: Kazu Hirata <kazu@codesourcery.com>
Cc: gdb-patches@sources.redhat.com
Subject: Re: [patch] Add support for fido.
Date: Tue, 26 Dec 2006 06:18:00 -0000 [thread overview]
Message-ID: <20061226061751.GB16237@caradoc.them.org> (raw)
In-Reply-To: <200612260203.kBQ23lTL007249@sparrowhawk.codesourcery.com>
On Mon, Dec 25, 2006 at 06:03:47PM -0800, Kazu Hirata wrote:
> +/* Watchpoints are always continuable for these targets. There's no
> + multi-arch way to set this yet since it still lives in the target
> + vector.
> +
> + FIXME: If the Fido port is ever submitted, this should move to
> + gdbarch. */
> +#define HAVE_CONTINUABLE_WATCHPOINT 1
Did you read my comment there? :-)
I admit I'm not quite sure what to do about it. Because of the sorts
of targets which define HAVE_CONTINUABLE_WATCHPOINT, this may be
difficult to untangle.
--
Daniel Jacobowitz
CodeSourcery
next prev parent reply other threads:[~2006-12-26 6:18 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-12-26 2:03 Kazu Hirata
2006-12-26 6:18 ` Daniel Jacobowitz [this message]
2006-12-26 14:07 ` Mark Kettenis
2007-10-07 18:12 Kazu Hirata
2007-10-08 23:57 ` Daniel Jacobowitz
2007-10-11 14:23 ` Kazu Hirata
2007-10-11 14:24 ` Daniel Jacobowitz
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=20061226061751.GB16237@caradoc.them.org \
--to=dan@codesourcery.com \
--cc=gdb-patches@sources.redhat.com \
--cc=kazu@codesourcery.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