From: Simon Marchi <simon.marchi@polymtl.ca>
To: Pedro Alves <palves@redhat.com>
Cc: Simon Marchi <simon.marchi@ericsson.com>, gdb-patches@sourceware.org
Subject: Re: [PATCH] Add "thread-group id" and "id in thread-group" info to -thread-info output
Date: Fri, 24 Feb 2017 20:32:00 -0000 [thread overview]
Message-ID: <406b48a3c072be59789e368a2904af77@polymtl.ca> (raw)
In-Reply-To: <480e785582e3631a5f693080f9855d2a@polymtl.ca>
On 2017-02-24 15:22, Simon Marchi wrote:
> - The type of the id-in-tg field (a string) assumes that a thread
> belongs to a single group. Currently, the only kind of "thread-group"
> we have is inferiors. The thread-group terminology suggests that in
> the future we might have other kinds of thread groups, like
> user-defined arbitrary groups. Otherwise, why would MI use "thread
> group" instead of "inferior"? Because of this, do you think that the
> type of the field will be limiting? For example, should we document
> right that this field can be a list, when a thread is part of multiple
> groups, for example?
Sorry, this paragraph should have referred to the "tg-id" field.
Although the "id-in-tg" makes sense when talking about an inferior
thread group, but not so much when talking about other kinds of thread
groups. If we have additional kinds of thread groups, they might not
assign their own specific ids to threads.
next prev parent reply other threads:[~2017-02-24 20:32 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-01-19 14:42 Simon Marchi
2017-01-19 14:55 ` Luis Machado
2017-01-19 14:57 ` Simon Marchi
2017-02-20 16:18 ` Simon Marchi
2017-02-23 19:50 ` Pedro Alves
2017-02-24 20:22 ` Simon Marchi
2017-02-24 20:32 ` Simon Marchi [this message]
2017-03-15 21:36 ` Simon Marchi
2017-03-17 15:27 ` Pedro Alves
2017-03-17 15:26 ` Pedro Alves
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=406b48a3c072be59789e368a2904af77@polymtl.ca \
--to=simon.marchi@polymtl.ca \
--cc=gdb-patches@sourceware.org \
--cc=palves@redhat.com \
--cc=simon.marchi@ericsson.com \
/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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).