Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Pedro Alves <pedro_alves@portugalmail.pt>
To: gdb-patches@sourceware.org
Cc: Michael Snyder <msnyder@specifix.com>
Subject: Re: [RFA] set/show enable-software-singlestep
Date: Wed, 25 Jun 2008 01:40:00 -0000	[thread overview]
Message-ID: <200806242107.22651.pedro_alves@portugalmail.pt> (raw)
In-Reply-To: <1214331534.3601.1211.camel@localhost.localdomain>

A Tuesday 24 June 2008 19:18:54, Michael Snyder wrote:
> There may be cases where gdb would be inclined to use
> software singlestep, but you might not want it to.  Examples:

I understand you want this for reverse debugging, so let me ask:

>  * "target remote" to a target such as a simulator that
>    would be able to support normal singlestep.

Should the support be reported by the stub instead?, as in:

Can the target (stub/debug api) do single-stepping?  Yes, cool.
No?  Bummer, will have to do software-singlestepping
on the GDB's side.

E.g, another similar issue with displaced stepping:
(hey you just touched that option :-) )

I'm working with a target that supports stepping 
off breakpoints on the stub side.  I was thinking of:

  Can the target (stub/debug api) step over breakpoints for me?
  Yes, cool.  No?  Bummer, will have to do displaced-stepping
  on the GDB's side.

>  * reverse debugging, where you can't predict the
>    "come-from" address of a jump instruction.

Should software-singlestepping *always* be disabled
while doing a reverse debug?  If so, why do we need the
command?  Shouldn't it be enforced in the code?

-- 
Pedro Alves


  parent reply	other threads:[~2008-06-24 20:07 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-06-24 18:43 Michael Snyder
2008-06-24 19:15 ` Daniel Jacobowitz
2008-06-24 19:32   ` Michael Snyder
2008-06-25 13:22     ` Joel Brobecker
2008-06-25 13:43       ` Daniel Jacobowitz
2008-06-25 14:15         ` Joel Brobecker
2008-06-25 14:33         ` Pedro Alves
2008-06-25 15:05           ` Daniel Jacobowitz
2008-06-25 15:38             ` Pedro Alves
     [not found]               ` <1214862215.3601.1525.camel@localhost.localdomain>
2008-07-10  2:46                 ` Michael Snyder
2008-07-10 11:07                   ` Pedro Alves
2008-07-10 22:47                     ` Daniel Jacobowitz
2008-07-12  2:31                       ` Michael Snyder
2008-07-12  2:28                     ` Michael Snyder
2008-06-25 14:35       ` Pedro Alves
2008-06-25 14:42         ` Joel Brobecker
2008-06-24 19:25 ` Eli Zaretskii
2008-06-24 19:34 ` Luis Machado
2008-06-24 20:22   ` Michael Snyder
2008-06-25  1:40 ` Pedro Alves [this message]
2008-06-25  6:15   ` 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=200806242107.22651.pedro_alves@portugalmail.pt \
    --to=pedro_alves@portugalmail.pt \
    --cc=gdb-patches@sourceware.org \
    --cc=msnyder@specifix.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