Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Joel Brobecker <brobecker@adacore.com>
To: Michael Snyder <msnyder@vmware.com>
Cc: "gdb-patches@sourceware.org" <gdb-patches@sourceware.org>,
		teawater <teawater@gmail.com>
Subject: Re: [RFA] Handle runtime loader dyn sym resolution in reverse
Date: Sat, 25 Oct 2008 16:10:00 -0000	[thread overview]
Message-ID: <20081025160945.GI29998@adacore.com> (raw)
In-Reply-To: <49028B5C.2000508@vmware.com>

> This is for both the main trunk and the record/replay branch
> (so I'd appreciate review by both Hui and a global maintainer).

I took a look. The patch itself is missing a little bit of context
(in terms of the code), so I wasn't sure whether I was looking at
inserting this hunk at the right place, but I think I found it:

      if (ecs->event_thread->step_over_calls == STEP_OVER_ALL)
        {
          /* We're doing a "next".

             Normal (forward) execution: set a breakpoint at the
             callee's return address (the address at which the caller
             will resume).

             Reverse (backward) execution.  set the step-resume
             breakpoint at the start of the function that we just
             stepped into (backwards), and continue to there.  When we
             get there, we'll need to single-step back to the caller.  */

          if (execution_direction == EXEC_REVERSE)

> 2008-10-24  Michael Snyder  <msnyder@vmware.com>
> 
> 	* infrun.c (handle_inferior_event): Handle dynamic symbol
> 	resolution in reverse.

Looks OK to me, but I don't understand why you check that stop_func_start
is zero. If I were to make a guess, it would be to quickly dismiss
the case were we reverse stepped into a function call, and so don't
need to check for trampolines (in other words, a CPU saver).

-- 
Joel


  parent reply	other threads:[~2008-10-25 16:10 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-10-25  3:04 Michael Snyder
2008-10-25  6:50 ` teawater
2008-10-25 16:10 ` Joel Brobecker [this message]
2008-10-26 14:15   ` teawater
2008-10-27  4:48   ` Michael Snyder
2008-10-27  5:00     ` Michael Snyder

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=20081025160945.GI29998@adacore.com \
    --to=brobecker@adacore.com \
    --cc=gdb-patches@sourceware.org \
    --cc=msnyder@vmware.com \
    --cc=teawater@gmail.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