From: Alain Magloire <alain@qnx.com>
To: Daniel Jacobowitz <drow@false.org>
Cc: Denis PILAT <denis.pilat@st.com>,
nickrob@snap.net.nz, gdb@sourceware.org
Subject: RE: info thread
Date: Mon, 25 Sep 2006 17:27:00 -0000 [thread overview]
Message-ID: <3518719F06577C4F85DA618E3C37AB9106B12B6C@nimbus.ott.qnx.com> (raw)
>
> I think you're thinking of -thread-list-ids. Ah, this is mi/674.
> It's also mi/1040. Both of which suggest *stopped :-)
>
> We could add the thread to -thread-list-ids, too.
>
> Something to keep in mind: the thread "extra info" is expensive to
> collect on some platforms, e.g. requires asking the remote stub for
> details on each individual thread.
>
Noted, but some platforms put some extra stuff in the output of "info
threads" like thread names, states, mutexes etc ... this information is then
retrieve by the IDE and shownn to the user.
It is my understanding, that the output is platform dependent. Are you
suggesting a new command to retrieve this info? I was hopping we could stuff
this in the output of -thread-list-ids.
Basically, we would like to retrieve more information on a thread what is
the best way for MI?
next reply other threads:[~2006-09-25 17:27 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-09-25 17:27 Alain Magloire [this message]
2006-09-25 17:36 ` Daniel Jacobowitz
2006-09-27 14:18 ` Denis PILAT
-- strict thread matches above, loose matches on Subject: below --
2006-09-28 14:35 Alain Magloire
2006-09-25 16:25 Alain Magloire
2006-09-25 15:25 Alain Magloire
2006-09-25 15:31 ` Daniel Jacobowitz
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
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
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=3518719F06577C4F85DA618E3C37AB9106B12B6C@nimbus.ott.qnx.com \
--to=alain@qnx.com \
--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