Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Pedro Alves <pedro@codesourcery.com>
To: Daniel Jacobowitz <drow@false.org>
Cc: gdb-patches@sourceware.org,
	 Joel Brobecker <brobecker@adacore.com>,
	 Michael Snyder <msnyder@specifix.com>
Subject: Re: [RFA] set/show enable-software-singlestep
Date: Wed, 25 Jun 2008 15:38:00 -0000	[thread overview]
Message-ID: <200806251603.51908.pedro@codesourcery.com> (raw)
In-Reply-To: <20080625144215.GA12011@caradoc.them.org>

A Wednesday 25 June 2008 15:42:15, Daniel Jacobowitz escreveu:
> On Wed, Jun 25, 2008 at 03:14:38PM +0100, Pedro Alves wrote:
> > A Wednesday 25 June 2008 14:34:57, Daniel Jacobowitz wrote:
> > > I think it should already be auto.  can-use-software-singlestep is
> > > unintuitive - either do use it, don't use it, or use GDB's best
> > > judgement.  And if the user selects to use it and it isn't supported,
> > > that's an error when we next want to singlestep.  WDYT?
> >
> > Well, not really auto.  If a ARM stub does software singlestepping itself
> > (say we add it to gdbserver), gdb will still do software
> > single-stepping (breakpoint dance), wont it?
>
> What Joel said elsewhere in the thread just now.  If we get a stub
> that reports definitively that it can single step, that should take
> priority over GDB knowing that software singlestep is implemented for
> this architecture.
>

What I said elsewhere in the thread just now.  :-)  The stub should
report it, and a new target method is required, that takes precedence
for stepping operations.

> Um, uh-oh.  This will break the overloading of software single step
> for bypassing atomic operations.  Clearly more thought is required!
>

The stub should just either step it all atomically, and GDB sees
only one SIGTRAP, or we force continuing over the sequence with a
single-step breakpoint (as we do today), not telling the
stub to step at all (as we don't do today...).  We seems we need
to distinguish this in the reporting mechanism.  Another issue is
that the atomic operations bypassing is implemented inside
the software_singlestepping gdbarch methods.  It should be
factored out.

> Another unfortunate note: we can't trust the vCont reply for this even
> though it's clearly the right thing :-(  Since current versions of GDB
> reject replies without s/S.

Yep, I noticed that.  We'll need something else, probably
qSupported (if we're thinking of supporting multi arch
stubs, care must be taken here as well).

-- 
Pedro Alves


  reply	other threads:[~2008-06-25 15:04 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 [this message]
     [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
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=200806251603.51908.pedro@codesourcery.com \
    --to=pedro@codesourcery.com \
    --cc=brobecker@adacore.com \
    --cc=drow@false.org \
    --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