public inbox for gdb-patches@sourceware.org
 help / color / mirror / Atom feed
From: Tom Tromey <tom@tromey.com>
To: Alexey Lapshin via Gdb-patches <gdb-patches@sourceware.org>
Cc: "tom@tromey.com" <tom@tromey.com>,
	 Alexey Lapshin <alexey.lapshin@espressif.com>,
	 Alexey Gerenkov <alexey.gerenkov@espressif.com>,
	 Anton Maklakov <anton.maklakov@espressif.com>,
	 Ivan Grokhotkov <ivan@espressif.com>
Subject: Re: [PATCH] gdb/python: initialize Python without signal handlers
Date: Tue, 20 Dec 2022 13:24:27 -0700	[thread overview]
Message-ID: <87tu1pkemc.fsf@tromey.com> (raw)
In-Reply-To: <6ffe1d07cf0a8dc0b455729d8a3cb9fa66c1f2fe.camel@espressif.com> (Alexey Lapshin via Gdb-patches's message of "Wed, 9 Nov 2022 20:40:44 +0000")

>> Could you say what these issues are and why it's desirable to make
>> this change for all hosts?

Alexey> The issues related to signal handlings. For Windows builds CTRL+C does
Alexey> not work.

We fixed this a different way.

Alexey> So, there is no reason to set default Python signal handlings
Alexey> that could differ from version to version And it's better to
Alexey> handle all signals in GDB itself, not in third-party libraries

This makes sense but I wonder if there are other impacts from this
change that we wouldn't want.  For example, if it affects Python scripts
running in gdb.

Tom

  reply	other threads:[~2022-12-20 20:25 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-11-09 19:42 Alexey Lapshin
2022-11-09 20:12 ` Tom Tromey
2022-11-09 20:40   ` Alexey Lapshin
2022-12-20 20:24     ` Tom Tromey [this message]
2022-12-21 16:12       ` Alexey Lapshin

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=87tu1pkemc.fsf@tromey.com \
    --to=tom@tromey.com \
    --cc=alexey.gerenkov@espressif.com \
    --cc=alexey.lapshin@espressif.com \
    --cc=anton.maklakov@espressif.com \
    --cc=gdb-patches@sourceware.org \
    --cc=ivan@espressif.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).