Mirror of the gdb mailing list
 help / color / mirror / Atom feed
From: "Rich Wagner" <richwagner@tilera.com>
To: "Daniel Jacobowitz" <drow@false.org>
Cc: <gdb@sourceware.org>
Subject: RE: "thread", "thread apply" and "step" ?
Date: Wed, 06 Aug 2008 17:38:00 -0000	[thread overview]
Message-ID: <BCB185E6A8E1DF4BAD610F00CD32CE0D02F9844F@exchange1.tad.internal.tilera.com> (raw)
In-Reply-To: <20080805202358.GB14077@caradoc.them.org>

Thanks Daniel:  I tried my experiments using GDB 6.8 and it does handle
the thread/step combinations sensibly.  To be specific, both:

    thread X
    step

and:

    thread apply X step

stepped thread X, even though the previous breakpoint-hit was in a
different thread than X.

-- Rich



-----Original Message-----
From: Daniel Jacobowitz [mailto:drow@false.org] 
Sent: Tuesday, August 05, 2008 4:24 PM
To: Rich Wagner
Cc: gdb@sourceware.org
Subject: Re: "thread", "thread apply" and "step" ?

On Tue, Aug 05, 2008 at 04:11:14PM -0400, Rich Wagner wrote:
> I'm using "gdb --version":
> 
>             GNU gdb Red Hat Linux (6.3.0.0-1.132.EL4rh)

Could you try 6.8, or even better a CVS snapshot, and see if it still
does this?  That release is several years old.

I think GDB does step the correct thread nowadays.

> P.S.  Where I work, we also use a customized version of gdb where we 
> provide our own RSP interpreter, because the customized version is 
> used for remote debugging.  Would the introduction of RSP change 
> things as they relate to threads and stepping?  I'm assuming the
"official"
> GDB-spec-based answers would necessarily apply to an RSP-based debug 
> session, but I mention RSP in case it affects things.

If you implement vCont, the serial protocol should work just as well.

--
Daniel Jacobowitz
CodeSourcery


  parent reply	other threads:[~2008-08-06 17:38 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-08-05 20:11 Rich Wagner
2008-08-05 20:24 ` Daniel Jacobowitz
2008-08-06  4:42   ` Michael Snyder
2008-08-06 11:20     ` Daniel Jacobowitz
2008-08-06 12:45     ` Pedro Alves
2008-08-06 17:38   ` Rich Wagner [this message]
2008-08-06  4:41 ` Michael Snyder
2008-08-06  5:17   ` Vladimir Prus

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=BCB185E6A8E1DF4BAD610F00CD32CE0D02F9844F@exchange1.tad.internal.tilera.com \
    --to=richwagner@tilera.com \
    --cc=drow@false.org \
    --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