Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Daniel Jacobowitz <drow@false.org>
To: Manoj Iyer <manjo@austin.ibm.com>
Cc: gdb-patches@sources.redhat.com
Subject: Re: [RFC] switch-threads.exp added tests.
Date: Tue, 14 Jun 2005 19:50:00 -0000	[thread overview]
Message-ID: <20050614195031.GA21575@nevyn.them.org> (raw)
In-Reply-To: <Pine.LNX.4.58.0506141408560.17509@lazy>

On Tue, Jun 14, 2005 at 02:35:05PM -0500, Manoj Iyer wrote:
> +gdb_test "info threads" "\\* .*2 Thread.*.LWP.* .*thread_func.*"
> +gdb_test "thread 1" ".*Switching to thread 1.*"
> +gdb_test "next" ".*foo \\(\\).*\[0-9\]*"
> +gdb_test "thread 2" ".*Switching to thread 2.*"

The numbers of threads depend on the operating system, and on the order
in which GDB notices new threads.  For instance the LinuxThreads
manager thread, or a remote target which does not report new threads
immediately.

Also the format of "info threads" output is target specific.  LWP comes
from the Linux specific native code.

-- 
Daniel Jacobowitz
CodeSourcery, LLC


      reply	other threads:[~2005-06-14 19:50 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-06-14 19:46 Manoj Iyer
2005-06-14 19:50 ` Daniel Jacobowitz [this message]

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=20050614195031.GA21575@nevyn.them.org \
    --to=drow@false.org \
    --cc=gdb-patches@sources.redhat.com \
    --cc=manjo@austin.ibm.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