Mirror of the gdb mailing list
 help / color / mirror / Atom feed
From: Mark Kettenis <mark.kettenis@xs4all.nl>
To: drow@false.org
Cc: nickrob@snap.net.nz, denis.pilat@st.com, gdb@sourceware.org
Subject: Re: info thread
Date: Sat, 23 Sep 2006 19:06:00 -0000	[thread overview]
Message-ID: <200609231905.k8NJ5ucX001839@elgar.sibelius.xs4all.nl> (raw)
In-Reply-To: <20060919210316.GA17479@nevyn.them.org> (message from Daniel 	Jacobowitz on Tue, 19 Sep 2006 17:03:16 -0400)

> Date: Tue, 19 Sep 2006 17:03:16 -0400
> From: Daniel Jacobowitz <drow@false.org>
> 
> This isn't really relevant.  It breaks down into just a few parts in GDB
> parlance:
> 
> - The GDB ID.  That's "1", "2", et cetera in your example.
> - The thread ID, produced by to_pid_to_str, e.g. "Thread -BLAH (LWP
> BLAH)".  This is just a string.
> - The thread extra info.  Not present in your example, but e.g.
> "(Exiting)" or "(not ready)".
> - The thread's current stack frame.
> 
> That last, I think, is not useful in MI.  There's commands to fetch it
> when it's wanted, and it might not be by some consumers.  And it will
> show up with -thread-select already.  So, I would recommend including
> only the GDB ID (as from -thread-list-ids) and the additional
> information.

Note that the formatting of the thread ID produced by to_pid_to_str is
highly dependent on the specific threads model in use.  The thread
extra info is also mostly free-form.  That means it might not be wise
to export that information in the MI interface.

Mark


  reply	other threads:[~2006-09-23 19:06 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-09-18 21:49 Nick Roberts
2006-09-19 13:16 ` Denis PILAT
2006-09-19 14:23   ` Daniel Jacobowitz
2006-09-19 20:55   ` Nick Roberts
2006-09-19 21:03     ` Daniel Jacobowitz
2006-09-23 19:06       ` Mark Kettenis [this message]
2006-09-23 21:59         ` Daniel Jacobowitz
2006-09-25 14:49           ` Denis PILAT
2006-09-25 14:52             ` Daniel Jacobowitz
2006-09-25 18:39           ` Michael Snyder
2006-09-25 15:25 Alain Magloire
2006-09-25 15:31 ` Daniel Jacobowitz
2006-09-25 16:25 Alain Magloire
2006-09-25 17:27 Alain Magloire
2006-09-25 17:36 ` Daniel Jacobowitz
2006-09-27 14:18 ` Denis PILAT
2006-09-28 14:35 Alain Magloire

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=200609231905.k8NJ5ucX001839@elgar.sibelius.xs4all.nl \
    --to=mark.kettenis@xs4all.nl \
    --cc=denis.pilat@st.com \
    --cc=drow@false.org \
    --cc=gdb@sourceware.org \
    --cc=nickrob@snap.net.nz \
    /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