Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Daniel Jacobowitz <drow@false.org>
To: Michael Snyder <msnyder@redhat.com>
Cc: Eli Zaretskii <eliz@gnu.org>, gdb-patches@sources.redhat.com
Subject: Re: [RFA] Reverse debugging, part 2/3: core interface
Date: Thu, 20 Apr 2006 19:52:00 -0000	[thread overview]
Message-ID: <20060420195154.GB22563@nevyn.them.org> (raw)
In-Reply-To: <4447E5B2.1080601@redhat.com>

On Thu, Apr 20, 2006 at 12:49:06PM -0700, Michael Snyder wrote:
> Good catch.  It should probably be get_frame_pc.
> You agree?

Yep.

> >>+    {
> >>+      /* Set breakpoint and continue.  */
> >>+      breakpoint = 
> >>+	set_momentary_breakpoint (sal, 
> >>+				  get_frame_id (get_selected_frame (NULL)),
> >>+				  bp_breakpoint);
> >
> >...above you used get_current_frame, here you used get_selected_frame.
> >Which is it?  I think that it should be the selected frame in all three
> >cases, by analogy with finish, and there should probably be a similar
> >error for cases without a caller.
> 
> Oh man, you're making my head hurt.  Which is, I suppose, a good thing.

Only fair, you made my brain ache this morning.

> What's the difference, now?  Is 'current_frame' the execution frame,
> and 'selected_frame' the displayed one?  (ie. the "up/down" one?)
> 
> If that's the case, then I think you're right, it should be
> the selected frame.

That's right.

-- 
Daniel Jacobowitz
CodeSourcery


      reply	other threads:[~2006-04-20 19:52 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <442DAA95.6050708@redhat.com>
2006-04-01 12:34 ` Eli Zaretskii
2006-04-01 16:10   ` Daniel Jacobowitz
2006-04-01 16:24     ` Eli Zaretskii
2006-04-17 23:42   ` Michael Snyder
2006-04-18  9:04     ` Eli Zaretskii
2006-04-20 16:00     ` Daniel Jacobowitz
2006-04-20 19:49       ` Michael Snyder
2006-04-20 19:52         ` 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=20060420195154.GB22563@nevyn.them.org \
    --to=drow@false.org \
    --cc=eliz@gnu.org \
    --cc=gdb-patches@sources.redhat.com \
    --cc=msnyder@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