Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Michael Snyder <msnyder@specifix.com>
To: Daniel Jacobowitz <drow@false.org>
Cc: Pedro Alves <pedro@codesourcery.com>,
	gdb-patches@sourceware.org,
	Joel Brobecker <brobecker@adacore.com>
Subject: Re: [RFA] set/show enable-software-singlestep
Date: Sat, 12 Jul 2008 02:31:00 -0000	[thread overview]
Message-ID: <1215829898.3549.235.camel@localhost.localdomain> (raw)
In-Reply-To: <20080710224727.GA20521@caradoc.them.org>

On Thu, 2008-07-10 at 18:47 -0400, Daniel Jacobowitz wrote:
> On Thu, Jul 10, 2008 at 12:07:19PM +0100, Pedro Alves wrote:
> > I had understood the consensus was that the command would be
> > useful for now.
> > 
> > It would be really nice if someone that had a target that
> > always required disabling software-singlestepping stepped forward
> > to add the GDB/remote smarts to do it automatically, though.  ;-)
> 
> I'd like to have some conclusion on how normal software single step
> and special software single step interact.  Are all the things handled
> in GDB's software single step routine also the responsibility of any
> stub that claims single step support?
> 
> Which is not how it works today - we let a powerpc gdbserver single
> step most things, but detect atomic sequences in the client.  This
> avoids duplicating the logic across all stubs, but is slower.
> 
> And do these special stepping types get turned off if you disable
> software single stepping manually?

Well, it seems to me that "normal single-step" is the base
case, and "software single-step" is the special case.

By telling gdb *not* to use software single-step, we're
just telling it to revert to the "base" behavior, whatever
that might be.

It doesn't seem to me that the non-software-singlestep
should then be obliged to emulate everything that might
have been done by the special-case software singlestep.




  reply	other threads:[~2008-07-12  2:31 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 [this message]
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
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=1215829898.3549.235.camel@localhost.localdomain \
    --to=msnyder@specifix.com \
    --cc=brobecker@adacore.com \
    --cc=drow@false.org \
    --cc=gdb-patches@sourceware.org \
    --cc=pedro@codesourcery.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