Mirror of the gdb mailing list
 help / color / mirror / Atom feed
From: Daniel Jacobowitz <drow@false.org>
To: Jon Ringle <jon.ringle@comdial.com>
Cc: SlickEdit Support <support@slickedit.com>, gdb@sources.redhat.com
Subject: Re: thread id is lost when viewing list of threads in slickedit
Date: Fri, 23 Sep 2005 19:57:00 -0000	[thread overview]
Message-ID: <20050923195736.GA9159@nevyn.them.org> (raw)
In-Reply-To: <200509231538.36201.jon.ringle@comdial.com>

On Fri, Sep 23, 2005 at 03:38:36PM -0400, Jon Ringle wrote:
> CC'ing gdb mailing list this issue. It seems that via the MI interface thread
> ID information is lost. Is there any way from the MI interface to get the
> thread IDs that seem to be missing?

The thread ID is not the third word, it's everything from the thread
number to the thread PC.  They're freeform, depending on the target, et
cetera.  So it's "thread 8201" and GDB tries to give you something
useful.  If you upgrade to NPTL, you'll find they get a lot less
intelligible.

You'd need an implementation of the documented -thread-info or
-thread-list-all-threads commands, which have never been defined.


Interesting, another item for my MI-using tools list...

-- 
Daniel Jacobowitz
CodeSourcery, LLC


  reply	other threads:[~2005-09-23 19:57 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <ECCC6E9907B4CD4A83260A191A91F20E6AC697@wampa.office.slickedit.com>
2005-09-23 19:40 ` Jon Ringle
2005-09-23 19:57   ` Daniel Jacobowitz [this message]
2005-09-23 20:32     ` Jon Ringle

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=20050923195736.GA9159@nevyn.them.org \
    --to=drow@false.org \
    --cc=gdb@sources.redhat.com \
    --cc=jon.ringle@comdial.com \
    --cc=support@slickedit.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