From: Daniel Jacobowitz <drow@false.org>
To: Vladimir Prus <ghost@cs.msu.su>
Cc: gdb-patches@sources.redhat.com
Subject: Re: [RFA] Ignore breakpoints when reading memory.
Date: Mon, 21 Jan 2008 18:37:00 -0000 [thread overview]
Message-ID: <20080121183729.GA28092@caradoc.them.org> (raw)
In-Reply-To: <fn2o0b$oti$1@ger.gmane.org>
On Mon, Jan 21, 2008 at 09:24:12PM +0300, Vladimir Prus wrote:
> So, is it OK to commit?
No, please see the questions from my mail upthread - it's clear that
there is at least one user that wants to check if the breakpoint is
still inserted so we need a way to do that. And read_memory_nobpt
shouldn't hang around duplicating this work.
--
Daniel Jacobowitz
CodeSourcery
prev parent reply other threads:[~2008-01-21 18:37 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-12-01 11:19 Vladimir Prus
2007-12-04 18:14 ` Mark Kettenis
2007-12-04 19:12 ` Jim Blandy
2008-01-21 17:19 ` Jim Blandy
2007-12-04 19:22 ` Daniel Jacobowitz
2007-12-05 22:31 ` Jim Blandy
2007-12-13 19:23 ` Vladimir Prus
2008-01-21 17:20 ` Jim Blandy
2008-01-21 18:24 ` Vladimir Prus
2008-01-21 18:37 ` 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=20080121183729.GA28092@caradoc.them.org \
--to=drow@false.org \
--cc=gdb-patches@sources.redhat.com \
--cc=ghost@cs.msu.su \
/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