Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Pedro Alves <palves@redhat.com>
To: "André Pönitz" <apoenitz@t-online.de>
Cc: Joel Brobecker <brobecker@adacore.com>,
	Eli Zaretskii <eliz@gnu.org>,
	gdb-patches@sourceware.org
Subject: Re: [RFA 2/2][master only] gdb/windows-nat.c: Get rid of main_thread_id global
Date: Mon, 22 Apr 2019 17:29:00 -0000	[thread overview]
Message-ID: <7f39cca0-c200-430e-e885-32cc347207d0@redhat.com> (raw)
In-Reply-To: <20190422152327.GA10697@klara.mpi.htwm.de>

On 4/22/19 4:23 PM, André Pönitz wrote:
> On Mon, Apr 22, 2019 at 03:24:46PM +0100, Pedro Alves wrote:
>> I don't see the asymmetry (silent at creation, not silent at destruction)
>> in this particular case as surprising [...]
> 
> It's not surprising, but it's inconsistent 
> and causes extra work in
> cases one wants to mechanically examine such output.

I'm curious about what extra work you're thinking of.  Can't think of
anything significant.

But do note that this discussion does not affect MI.

So what do you propose?  My proposal kept these two ideas in mind:

- be quiet wrt to threads with single-threaded programs.
- inform the user the main thread exited while other threads stay running.

Thanks,
Pedro Alves


  reply	other threads:[~2019-04-22 17:29 UTC|newest]

Thread overview: 25+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-04-16 22:33 Windows native GDB event handling enhancement Joel Brobecker
2019-04-16 22:33 ` [RFA 1/2][master+8.3] (Windows) fix thr != nullptr assert failure in delete_thread_1 Joel Brobecker
2019-04-18 14:52   ` Pedro Alves
2019-04-18 15:04     ` Pedro Alves
2019-04-16 22:33 ` [RFA 2/2][master only] gdb/windows-nat.c: Get rid of main_thread_id global Joel Brobecker
     [not found]   ` <83imvcg0ud.fsf@gnu.org>
2019-04-17 17:38     ` Joel Brobecker
2019-04-17 18:29       ` Eli Zaretskii
2019-04-17 22:17         ` Joel Brobecker
2019-04-18 12:52           ` Eli Zaretskii
2019-04-18 14:54             ` Joel Brobecker
2019-04-18 16:27           ` Pedro Alves
2019-04-19 20:43             ` Joel Brobecker
2019-04-22 14:24               ` Pedro Alves
2019-04-22 15:20                 ` André Pönitz
2019-04-22 17:29                   ` Pedro Alves [this message]
2019-04-22 21:42                     ` André Pönitz
2019-04-23  5:54                       ` Eli Zaretskii
2019-04-24 20:10                         ` André Pönitz
2019-04-25  5:39                           ` Eli Zaretskii
2019-04-23 11:42                       ` Pedro Alves
2019-04-28 16:58 ` [v2] Windows native GDB event handling enhancement Joel Brobecker
2019-04-28 16:58   ` [RFA v2 1/2][master+8.3] (Windows) fix thr != nullptr assert failure in delete_thread_1 Joel Brobecker
2019-04-28 16:58   ` [RFA v2 2/2][master only] gdb/windows-nat.c: Get rid of main_thread_id global Joel Brobecker
2019-04-30 13:00   ` [v2] Windows native GDB event handling enhancement Pedro Alves
2019-04-30 21:04     ` pushed(master+8.3): " Joel Brobecker

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=7f39cca0-c200-430e-e885-32cc347207d0@redhat.com \
    --to=palves@redhat.com \
    --cc=apoenitz@t-online.de \
    --cc=brobecker@adacore.com \
    --cc=eliz@gnu.org \
    --cc=gdb-patches@sourceware.org \
    /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