From: Tom Tromey <tromey@adacore.com>
To: Hannes Domani <ssbssa@yahoo.de>
Cc: Hannes Domani via Gdb-patches <gdb-patches@sourceware.org>,
Tom Tromey <tromey@adacore.com>
Subject: Re: [PATCH] [RFC] Move SetConsoleCtrlHandler calls to async thread
Date: Thu, 01 Dec 2022 14:22:04 -0700 [thread overview]
Message-ID: <87zgc6lszn.fsf@tromey.com> (raw)
In-Reply-To: <1754067492.12464828.1669921602659@mail.yahoo.com> (Hannes Domani's message of "Thu, 1 Dec 2022 19:06:42 +0000 (UTC)")
>>>>> Hannes Domani <ssbssa@yahoo.de> writes:
>> Anyway, I managed to test C-c by using remmina (RDP client) and then
>> running gdb in the console provided there. I used conemu which I gather
>> opened some kind of Cygwin shell.
> I'm not sure if C-c works the same inside of Cygwin.
Me neither. I'll see if I can try a different console tomorrow.
> Note that it also makes a difference if you started a process with
> 'set new-console on' enabled (which is what I always have set).
Ok, I wasn't even aware of this. And, I see there's also "new-group",
which defaults to true.
Looking into this, first, when would anyone want to disable new-group?
Second, new-console disables new-group. From the MS docs:
CREATE_NEW_PROCESS_GROUP
[...]
This flag is ignored if specified with CREATE_NEW_CONSOLE.
So this may help explain the differences.
I'll also experiment with new-console tomorrow.
Tom
next prev parent reply other threads:[~2022-12-01 21:22 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20221128191526.1426-1-ssbssa.ref@yahoo.de>
2022-11-28 19:15 ` Hannes Domani
2022-12-01 17:30 ` Tom Tromey
2022-12-01 19:06 ` Hannes Domani
2022-12-01 21:22 ` Tom Tromey [this message]
2022-12-02 16:12 ` Tom Tromey
2022-12-02 22:22 ` Tom Tromey
2022-12-02 22:51 ` Hannes Domani
2022-12-05 18:54 ` Tom Tromey
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=87zgc6lszn.fsf@tromey.com \
--to=tromey@adacore.com \
--cc=gdb-patches@sourceware.org \
--cc=ssbssa@yahoo.de \
/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).