From: Vladimir Prus <ghost@cs.msu.su>
To: gdb-patches@sources.redhat.com
Subject: Re: [RFA] Ignore breakpoints when reading memory.
Date: Mon, 21 Jan 2008 18:24:00 -0000 [thread overview]
Message-ID: <fn2o0b$oti$1@ger.gmane.org> (raw)
In-Reply-To: <8f2776cb0801210920r1ea9a0f7he8c78298787b9422@mail.gmail.com>
Jim Blandy wrote:
> On Dec 5, 2007 1:34 PM, Jim Blandy <jimb@codesourcery.com> wrote:
>> > Are there any sites that need to see the breakpoint? For instance,
>> > look at ppc_linux_memory_remove_breakpoint.
>>
>> The code I'm presently working on would like to see breakpoints, to my
>> surprise.
>
> This code evolved, and it no longer needs to see breakpoints. I have
> no objections to this patch.
So, is it OK to commit?
- Volodya
next prev parent reply other threads:[~2008-01-21 18:24 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 [this message]
2008-01-21 18:37 ` 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='fn2o0b$oti$1@ger.gmane.org' \
--to=ghost@cs.msu.su \
--cc=gdb-patches@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