From: Nick Roberts <nickrob@snap.net.nz>
To: Joel Brobecker <brobecker@adacore.com>
Cc: Vladimir Prus <vladimir@codesourcery.com>,
gdb-patches@sources.redhat.com
Subject: Re: [RFA] Report the main thread.
Date: Sun, 11 May 2008 22:33:00 -0000 [thread overview]
Message-ID: <18471.27891.225239.186380@kahikatea.snap.net.nz> (raw)
In-Reply-To: <20080511155232.GH28890@adacore.com>
> There has been a discussion earlier about the merits and drawbacks
> of adding the main "thread" to the list of threads when debugging
> an application that doesn't use threads. We only considered the
> perspective of the user, but there is indeed the case of front-ends.
> Assuming that the decision still stands, I think it is reasonable
> to ask the front-ends to check that there is more than one thread
> before going into "thread" mode. I understand that this is making
> things a little more complicated, but it shouldn't be that hard.
>
> On the other hand, if there is a way to detect that the new "thread"
> is from an unthreaded program, we could decide to not emit the
> notification. But I would like things to be consistent - it should
> be the same for both CLI, MI and annotations.
CLI and MI are both interpreters. Annotations are just a markup of CLI
output, so I don't think they should be considered equally.
I don't see the need to report the main thread but if Pedro and Vladimir do,
then I'm happy to live with that. If I propose an annotation that doesn't
report the main thread, then since they won't be using it, I would expect that
they won't object. Furthermore, since annotations would never be used with MI
and they are destined for removal anyway, trying to make them consistent seems
a pointless exercise.
--
Nick http://www.inet.net.nz/~nickrob
next prev parent reply other threads:[~2008-05-11 22:03 UTC|newest]
Thread overview: 38+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-05-10 18:00 Nick Roberts
2008-05-10 19:26 ` Vladimir Prus
2008-05-11 14:10 ` Nick Roberts
2008-05-11 14:45 ` Vladimir Prus
2008-05-11 15:52 ` Nick Roberts
2008-05-11 16:00 ` Vladimir Prus
2008-05-11 16:13 ` Nick Roberts
2008-05-11 16:41 ` Vladimir Prus
2008-05-11 22:19 ` Nick Roberts
2008-05-12 22:22 ` Michael Snyder
2008-05-11 20:19 ` Joel Brobecker
2008-05-11 21:10 ` Vladimir Prus
2008-05-11 22:33 ` Nick Roberts [this message]
2008-05-12 3:18 ` Daniel Jacobowitz
2008-05-12 16:11 ` Nick Roberts
2008-05-12 18:19 ` Daniel Jacobowitz
2008-05-10 19:42 ` Vladimir Prus
2008-05-10 22:12 ` Joel Brobecker
2008-05-11 14:29 ` Nick Roberts
-- strict thread matches above, loose matches on Subject: below --
2008-04-26 16:44 Vladimir Prus
2008-04-26 17:16 ` Mark Kettenis
2008-04-26 17:22 ` Daniel Jacobowitz
2008-04-26 17:31 ` Vladimir Prus
2008-04-26 21:05 ` Daniel Jacobowitz
2008-04-26 22:36 ` Vladimir Prus
2008-04-27 4:27 ` Nick Roberts
2008-04-27 9:03 ` Vladimir Prus
2008-04-27 11:14 ` Daniel Jacobowitz
2008-04-27 14:24 ` Nick Roberts
2008-04-27 13:53 ` Nick Roberts
2008-04-27 15:50 ` Daniel Jacobowitz
2008-04-27 16:07 ` Mark Kettenis
2008-04-27 16:07 ` Pedro Alves
2008-04-27 21:46 ` Mark Kettenis
2008-04-28 3:31 ` Pedro Alves
2008-04-27 18:25 ` Daniel Jacobowitz
2008-04-30 10:11 ` Vladimir Prus
2008-04-30 13:28 ` Daniel Jacobowitz
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=18471.27891.225239.186380@kahikatea.snap.net.nz \
--to=nickrob@snap.net.nz \
--cc=brobecker@adacore.com \
--cc=gdb-patches@sources.redhat.com \
--cc=vladimir@codesourcery.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