Mirror of the gdb mailing list
 help / color / mirror / Atom feed
From: Greg Law <glaw@undo-software.com>
To: Michael Snyder <msnyder@vmware.com>
Cc: Julian Smith <jsmith@undo-software.com>,
	  "gdb@sources.redhat.com" <gdb@sources.redhat.com>
Subject: Re: reverse-next doing repeated reverse-stepi's ?
Date: Thu, 24 Dec 2009 14:08:00 -0000	[thread overview]
Message-ID: <4B3370A2.8000701@undo-software.com> (raw)
In-Reply-To: <4B325D82.4010102@vmware.com>

Michael Snyder wrote:
> Julian Smith wrote:
>> I've been trying out reverse-next with UndoDB as a remote debug server,
>> and it looks like reverse-next works by doing repeated
>> `bs' (reverse-stepi) commands.
>>
>> I was expecting it to set breakpoints and do `bc' (reverse-continue)
>> commands, by analogy with normal forwards step etc.
>>
>> Am i doing something wrong here ? Or is this the expected behaviour ?
> 
> Short answer: this is expected behavior.
> 
> Forward-next works the same way, in general.
> Both forward-next and reverse-next will set breakpoints
> under some circumstances, but will often work by
> singlestepping.

If I understand correctly, when doing a 'next' gdb does something like:

while (PC in current line) {
  ptrace (PTRACE_SINGLESTEP)
  if (PC outside current function) {
    plant breakpoint at return address
    ptrace (PTRACE_CONT)
    remove breakpoint
  }
}

however, when doing a reverse-next, we don't see this.  We just see 
repeated reverse single-steps.  If trying to do a reverse-next over a 
non-trivial function, this can take a very long time.  Is this expected?


Greg

-- 
Greg Law, Undo Software                       http://undo-software.com/


  reply	other threads:[~2009-12-24 14:08 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-12-23 17:02 Julian Smith
2009-12-23 18:15 ` Michael Snyder
2009-12-24 14:08   ` Greg Law [this message]
2009-12-24 18:35     ` 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=4B3370A2.8000701@undo-software.com \
    --to=glaw@undo-software.com \
    --cc=gdb@sources.redhat.com \
    --cc=jsmith@undo-software.com \
    --cc=msnyder@vmware.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