Mirror of the gdb mailing list
 help / color / mirror / Atom feed
From: Michael Snyder <msnyder@specifix.com>
To: Joel Brobecker <brobecker@adacore.com>
Cc: gdb@sourceware.org
Subject: Re: Turn software singlestep off?
Date: Tue, 24 Jun 2008 03:12:00 -0000	[thread overview]
Message-ID: <1214277102.3601.1199.camel@localhost.localdomain> (raw)
In-Reply-To: <20080624025854.GA4484@adacore.com>

On Mon, 2008-06-23 at 22:58 -0400, Joel Brobecker wrote:
> > I thought there used to be, but now I can't find it.
> 
> I don't think there is such a switch either. I don't think it would
> be very hard to implement, though... And it could actually be useful
> on architectures such as Tru64 (I think) where we enable SW single step
> because the kernel stepping doesn't work for threaded program. Such
> a switch would probably give the user a chance to have better
> performance when debugging a program that doesn't use threads...
> It would be a pretty geeky switch, though, and I would be ready to
> bet that the number of people knowing about it would remain very small.

Thanks.  Sounds about right.

There could be other contexts where it would be useful.
Imagine you're talking to a remote target, but you (gdb)
don't really know what it is.

It could be a simulator.  Or a record/replay type of thing.
Something that wouldn't have a problem with singlestep, 
even though the native architecture would.

However, here's my real reason for asking:  I'm trying
to implement reverse debugging for mips.  Reverse
debugging and software singlestep don't mix very well.
GDB would have to figure out where to put the singlestep
breakpoint.  Singlestepping thru a jump, you can do that
going forward, but not going backward!   ;-)




  reply	other threads:[~2008-06-24  3:12 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-06-24  2:50 Michael Snyder
2008-06-24  2:59 ` Joel Brobecker
2008-06-24  3:12   ` Michael Snyder [this message]
2008-06-24 13:11 ` Daniel Jacobowitz

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=1214277102.3601.1199.camel@localhost.localdomain \
    --to=msnyder@specifix.com \
    --cc=brobecker@adacore.com \
    --cc=gdb@sourceware.org \
    /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