public inbox for gdb-patches@sourceware.org
 help / color / mirror / Atom feed
From: Pedro Alves <palves@redhat.com>
To: Simon Marchi <simon.marchi@polymtl.ca>
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, 17 Mar 2017 15:26:00 -0000	[thread overview]
Message-ID: <e05abd5f-af3d-3ec9-74ab-b225bc326c23@redhat.com> (raw)
In-Reply-To: <480e785582e3631a5f693080f9855d2a@polymtl.ca>

On 02/24/2017 08:22 PM, Simon Marchi wrote:

> While writing the documentation parts, these question popped to mind:
> 
> - 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"?  

The concept of MI thread groups was added way before the concept
of "inferiors" and inferior numbers was exposed to the user:

  https://sourceware.org/ml/gdb-patches/2008-11/msg00044.html

Back then the thread list was global, and we were starting to add
multi-process support to GDB.  The OS we were targeting (from Ericsson,
no less) had all processes running the same code (as if a bunch of forks),
which was convenient as it allowed for incremental progress all the
way until we got to real multi-inferior support a few releases later.  Back
then, MI thread groups mapped to "processes", and thread groups were
only created when we'd attach to a process.

Later on, when we added real GNU/Linux multi-inferior support (with the
addition of program spaces), we exposed the "prototype inferior" concept
to the user (i.e., the inferior now exists before the user types "run"), and
"thread groups" were re-purposed.  See:

  https://sourceware.org/ml/gdb-patches/2010-01/msg00358.html

Thanks,
Pedro Alves

      parent reply	other threads:[~2017-03-17 15:26 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
2017-03-15 21:36       ` Simon Marchi
2017-03-17 15:27         ` Pedro Alves
2017-03-17 15:26       ` Pedro Alves [this message]

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=e05abd5f-af3d-3ec9-74ab-b225bc326c23@redhat.com \
    --to=palves@redhat.com \
    --cc=gdb-patches@sourceware.org \
    --cc=simon.marchi@ericsson.com \
    --cc=simon.marchi@polymtl.ca \
    /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).