Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Denis PILAT <denis.pilat@st.com>
To: Nick Roberts <nickrob@snap.net.nz>
Cc: gdb-patches <gdb-patches@sourceware.org>
Subject: Re: New mi commands for threads
Date: Fri, 16 Mar 2007 08:40:00 -0000	[thread overview]
Message-ID: <45FA57F0.4030107@st.com> (raw)
In-Reply-To: <17913.46746.760751.573314@kahikatea.snap.net.nz>

Nick Roberts wrote:
> I think it's best to keep the patches separate unless the code changes
> overlap.
Ok I'll do that.
>
>
> I would put number-of-threads="6",current-thread-id="1" at the start so that
> they don't get lost behind the thread list (I know the output is only intended
> for the front end but it might make debugging of GDB easier and costs nothing).
>
> Lists use square brackets, information on each thread should be enclosed in
> curly brackets:
>
> threads=[{thread-id="6",frame={...},thread-extra-info="bla"},{thread-id="5",frame={...},thread-extra-info="bla"},...]
>
> I guess your output has been manually generated as thread-id="1" seems to
> duplicate some information.
This output is a side effect of the frame printing, the actual 
-thread-select command has the same. I'm going to have a look at how we 
can avoid it, but I think it will impact *-thread-select* as well.

About brackets, I see how they were used in *-thread-list-ids*, 
according to your comment, this one should use square brackets as well, 
am I right ?

About position of "number-of-threads" and "current-thread-id", I prefer 
them in front as well, but that would be not consistent with 
-thread-list-ids. But do we care about consistency with this one that 
seems to be not consistent with the MI list format  ? 
>
> I thought that the frame information was expensive to get and that it was
> agreed you could get it, if needed, using other MI commands anyway.
Yes it is, but I want to get rid of CLI commands and for front ends that 
want to get all informations, they could use this command if they need 
extra information. But I can add an option to include or not these 
information.
For remote (or on board) debugging, our front ends will emit 
*-thread-list-ids* to get only the list, and then *-thread-info* to 
focus only on the current thread.

But for "native and efficient" debugging, I guess a call to 
*-thread-list-all-threads* will do the job.
That will give us:
-thread-list-ids                 : gives list of thread ids + number of 
threads
-thread-list-all-threads         : gives the above + stack frame 
information per thread + current thread
-thread-list-all-threads --extra : gives the above + extra information 
per thread.



Thanks a lot for your feedback Nick,
-- 
Denis Pilat


  reply	other threads:[~2007-03-16  8:40 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-03-14 16:17 Denis PILAT
2007-03-15 21:12 ` Nick Roberts
2007-03-16  8:40   ` Denis PILAT [this message]
2007-03-16 23:43     ` Nick Roberts
2007-03-19 13:45       ` Denis PILAT

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=45FA57F0.4030107@st.com \
    --to=denis.pilat@st.com \
    --cc=gdb-patches@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