From: Daniel Jacobowitz <drow@false.org>
To: "Maciej W. Rozycki" <macro@mips.com>
Cc: gdb-patches@sourceware.org, "Maciej W. Rozycki" <macro@linux-mips.org>
Subject: Re: mips-tdep.c: Fix sw watchpoint-out-of-scope events
Date: Wed, 19 Sep 2007 13:16:00 -0000 [thread overview]
Message-ID: <20070919131640.GA29209@caradoc.them.org> (raw)
In-Reply-To: <Pine.LNX.4.61.0709191341240.27377@perivale.mips.com>
On Wed, Sep 19, 2007 at 02:05:02PM +0100, Maciej W. Rozycki wrote:
> Well, that sounds reasonable given the complication around getting things
> perfect here. Ideally the out-of-scope event should happen at the same
> place where "finish" from the function in question would stop; in my
> opinion at least.
Honestly, I'm not sure we should even be stopping when watchpoints go
out of scope. Anyway a patch to accept the call site as a PASS is pre-approved.
--
Daniel Jacobowitz
CodeSourcery
prev parent reply other threads:[~2007-09-19 13:16 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-09-11 16:24 Maciej W. Rozycki
2007-09-18 15:54 ` Daniel Jacobowitz
2007-09-19 12:31 ` Maciej W. Rozycki
2007-09-19 12:38 ` Daniel Jacobowitz
2007-09-19 13:05 ` Maciej W. Rozycki
2007-09-19 13:16 ` Daniel Jacobowitz [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=20070919131640.GA29209@caradoc.them.org \
--to=drow@false.org \
--cc=gdb-patches@sourceware.org \
--cc=macro@linux-mips.org \
--cc=macro@mips.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