Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Vladimir Prus <ghost@cs.msu.su>
To: gdb-patches@sources.redhat.com
Subject: Re: [RFA] Ignore breakpoints when reading memory.
Date: Thu, 13 Dec 2007 19:23:00 -0000	[thread overview]
Message-ID: <fjrq0i$g2t$1@ger.gmane.org> (raw)
In-Reply-To: <m33augq10f.fsf@codesourcery.com>

Jim Blandy wrote:

> 
> Daniel Jacobowitz <drow at false.org> writes:
>> On Sat, Dec 01, 2007 at 02:19:45PM +0300, Vladimir Prus wrote:
>>> 
>>> This commit prepares us for always-inserted-breakpoints mode.
>>> If breakpoints are always inserted, then reading the code memory
>>> will read the breakpoint instructions, not the original content.
>>> This patch makes us try to restore the original comments using
>>> the breakpoints table. OK?
>>
>> Doesn't this make the extra call in read_memory_nobpt redundant?
>>
>> 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.

Hmm, why?

I see two solutions:
1. Add new parameter to target_xfer_partial, telling whether breakpoint
content should be shown or restored. Pass that parameter whenever we
need to see breakpoints. That would need quite a bit of churn
everywhere.

2. Don't touch memory_xfer_partial at all. Audit all places where code
memory is accessed, and call restore_breakpoint_shadows explicitly.
Lots of work, likewise, but also eliminates the performance concerns.

Comments?

- Volodya



  reply	other threads:[~2007-12-13 17:57 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 [this message]
2008-01-21 17:20     ` Jim Blandy
2008-01-21 18:24       ` Vladimir Prus
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='fjrq0i$g2t$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