From: Denis PILAT <denis.pilat@st.com>
To: Nick Roberts <nickrob@snap.net.nz>, Daniel Jacobowitz <drow@false.org>
Cc: gdb@sourceware.org
Subject: Re: info thread
Date: Tue, 19 Sep 2006 13:16:00 -0000 [thread overview]
Message-ID: <450FED7C.1050902@st.com> (raw)
In-Reply-To: <17679.5055.729126.253019@kahikatea.snap.net.nz>
Nick Roberts wrote:
>>Sol 1 - developping a new MI command that gives the above target extra
>>information only (ie -thread-list-extra-info) or implementing a
>>non-implemented one with a parameter. I see in the doc that
>>-thread-list-all-threads is not specified for instance.
>>
>>
>>Then we need to modify Eclipse so that it uses MI command "-thread-list-ids"
>>plus this command to get all info. This can be an Eclipse contribution
>>as well, I need to ask to Eclipse maintainer as well.
>>
>>
>
>There is only a slot for -thread-list-all-threads and no implementation so I
>see no harm in using a new name, especially if your command doesn't list _all_
>the info. I'm not very familiar with debugging threaded applications but I
>think the command should be general and not just suited to your requirements.
>Also if there is a common usage pattern then I think it would be good if that
>information can be obtained with one MI command rather than two/many. That is
>the essence of many of the changes that I have made to MI.
>
>
Daniel wrote:
> I think we've got two visible options: make -thread-list-all-threads
> do exactly what you want, without stack information, or make
> -thread-info return the target extra info for the thread. Either
> makes sense to me. Might as well make -thread-list-all-threads
> do it.
Daniel, Nick,
Thanks for your answers.
Let's continue this thread on the gdb mailing list as Nick suggested.
I still don't have answer from the Eclipse community but reading my
email, it's not a surprise ... I think it was not so easy to read,
I was probably drunk when I wrote it.
Where can I find the specifications for the MI commands
-thread-list-all-threads and -thread-info ?
Denis
next prev parent reply other threads:[~2006-09-19 13:16 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 [this message]
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
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=450FED7C.1050902@st.com \
--to=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