Mirror of the gdb mailing list
 help / color / mirror / Atom feed
From: Nick Roberts <nickrob@snap.net.nz>
To: Denis PILAT <denis.pilat@st.com>
Cc: Daniel Jacobowitz <drow@false.org>, gdb@sourceware.org
Subject: Re: info thread
Date: Tue, 19 Sep 2006 20:55:00 -0000	[thread overview]
Message-ID: <17680.22719.512121.415472@kahikatea.snap.net.nz> (raw)
In-Reply-To: <450FED7C.1050902@st.com>

 > Where can I find the specifications for the MI commands 
 > -thread-list-all-threads and -thread-info ?

There is no specification so we can only guess what was intended.  Perhaps
-thread-info was just meant to give info for the selected thread which
presumably would not take long to compute even with all the details.  In any
case, as Daniel says, the problem is to devise one(s) which is/are generally
useful.

I would guess the reason that they haven't already been implemented is that
the other information is kernel/OS dependent e.g on GNU/Linux I get:


(gdb) inf threads
  5 Thread -1240261728 (LWP 2575)  0x00c12b68 in clone () from /lib/libc.so.6
  4 Thread -1229771872 (LWP 2574)  0x08048863 in myproc (ptr_i=0xbff15ca4)
    at pthreadtest.c:75
  3 Thread -1219282016 (LWP 2573)  0x00c12b68 in clone () from /lib/libc.so.6
  2 Thread -1208792160 (LWP 2572)  0x08048833 in myproc (ptr_i=0xbff15c9c)
    at pthreadtest.c:78
* 1 Thread -1208789312 (LWP 2554)  main () at pthreadtest.c:99

but presumably not all systems have the concept of a lightweight process,
and maybe the numbering of the threads is different.


-- 
Nick                                           http://www.inet.net.nz/~nickrob


  parent reply	other threads:[~2006-09-19 20:55 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 [this message]
2006-09-19 21:03     ` Daniel Jacobowitz
2006-09-23 19:06       ` Mark Kettenis
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=17680.22719.512121.415472@kahikatea.snap.net.nz \
    --to=nickrob@snap.net.nz \
    --cc=denis.pilat@st.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