Mirror of the gdb mailing list
 help / color / mirror / Atom feed
From: Daniel Jacobowitz <drow@false.org>
To: Wu Zhou <woodzltc@cn.ibm.com>
Cc: gdb@sourceware.org
Subject: Re: A little patch for two comments in infrun.c
Date: Tue, 30 May 2006 18:48:00 -0000	[thread overview]
Message-ID: <20060530182728.GA19251@nevyn.them.org> (raw)
In-Reply-To: <Pine.LNX.4.64.0605301602590.2773@localhost.localdomain>

On Tue, May 30, 2006 at 04:24:11PM +0800, Wu Zhou wrote:
> Hi,
> 
> I am reading the source of infrun.c, and having a couple questions about 
> two comments in the code:
> 
> First, in resume (int step, enum target_signal sig), one comment says:
> 
>   /* FIXME: calling breakpoint_here_p (read_pc ()) three times! */
> 
> Does this still make sense?  In function resume, there does exist three 
> call for breakpoint_here_p (read_pc ()).  But read_pc () might return 
> various values at various points.  The breakpoint chain maintained in 
> this function might also change as the execution proceeds.  So I am 
> thinking this comment doesn't make sense here.  Am I right?  Any error, 
> feel free to correct me.

That's why it hasn't been fixed yet :-)  It's wasteful, but not very
wasteful, because of the register cache.  The breakpoint chain
shouldn't change during the function; the singlestep breakpoint is
modified, but isn't on that chain.

I don't much care if you leave or remove the FIXME.


-- 
Daniel Jacobowitz
CodeSourcery


      parent reply	other threads:[~2006-05-30 18:27 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-05-30 17:14 Wu Zhou
2006-05-30 18:40 ` Jim Blandy
2006-05-30 18:48 ` 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=20060530182728.GA19251@nevyn.them.org \
    --to=drow@false.org \
    --cc=gdb@sourceware.org \
    --cc=woodzltc@cn.ibm.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