Mirror of the gdb mailing list
 help / color / mirror / Atom feed
From: Daniel Jacobowitz <drow@false.org>
To: PAUL GILLIAM <pgilliam@us.ibm.com>
Cc: Paul Koning <pkoning@equallogic.com>,
	mark.kettenis@xs4all.nl, 	gdb@sources.redhat.com
Subject: Re: Instrcutions that must not be stepped.
Date: Wed, 21 Jun 2006 01:17:00 -0000	[thread overview]
Message-ID: <20060620233526.GB14292@nevyn.them.org> (raw)
In-Reply-To: <1150842231.7608.8.camel@dufur.beaverton.ibm.com>

On Tue, Jun 20, 2006 at 03:23:51PM -0700, PAUL GILLIAM wrote:
> On Tue, 2006-06-20 at 16:17 -0400, Paul Koning wrote:
> > >>>>> "PAUL" == PAUL GILLIAM <pgilliam@us.ibm.com> writes:
> > 
> >  >> By the way, if stepping these atomic sequences proves to be a
> >  >> performance problem, you might want to consider implementing
> >  >> stepping them in the (Linux) kernel.
> > 
> >  PAUL> This would be cool.  It would be nice to be able to tell if the
> >  PAUL> kernel has support for this and let it handle atomic sequences
> >  PAUL> if it does.  Let GDB handle it if the kernel doesn't.
> > 
> > Similarly, in remote debugging, there should be a way to have the stub
> > handle it.  That means you may need some extensions to the stub
> > protocol to encode some new information...
> 
> Perhaps something in "qSupported" stuff Danial Jacobowitz is working on?

No, that's unrelated.  I think all you'll want is "step out of range"
on the GDB side, and let the stub handle everything else.

-- 
Daniel Jacobowitz
CodeSourcery


  reply	other threads:[~2006-06-20 23:35 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-06-08  2:27 PAUL GILLIAM
2006-06-08  3:50 ` Daniel Jacobowitz
2006-06-16  4:36   ` PAUL GILLIAM
2006-06-17 12:26     ` PAUL GILLIAM
2006-06-18  4:57       ` Mark Kettenis
2006-06-20 20:13         ` PAUL GILLIAM
2006-06-20 22:53           ` Paul Koning
2006-06-20 23:34             ` PAUL GILLIAM
2006-06-21  1:17               ` Daniel Jacobowitz [this message]
2006-06-09 14:12 John Yates
2006-06-09 14:28 ` Daniel Jacobowitz
2006-06-10  0:33   ` PAUL GILLIAM

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=20060620233526.GB14292@nevyn.them.org \
    --to=drow@false.org \
    --cc=gdb@sources.redhat.com \
    --cc=mark.kettenis@xs4all.nl \
    --cc=pgilliam@us.ibm.com \
    --cc=pkoning@equallogic.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