public inbox for gdb-patches@sourceware.org
 help / color / mirror / Atom feed
From: Alexey Lapshin <alexey.lapshin@espressif.com>
To: "gdb-patches@sourceware.org" <gdb-patches@sourceware.org>,
	"tom@tromey.com" <tom@tromey.com>
Cc: 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: Wed, 9 Nov 2022 20:40:44 +0000	[thread overview]
Message-ID: <6ffe1d07cf0a8dc0b455729d8a3cb9fa66c1f2fe.camel@espressif.com> (raw)
In-Reply-To: <87edub28g5.fsf@tromey.com>

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

The issues related to signal handlings. For Windows builds CTRL+C does
not work. Because it handles by Pyhton, not a GDB.
I don't know why it does not happen on Linux builds, but I believe that
signal handlers must not be set.
Also, documentation
(https://sourceware.org/gdb/onlinedocs/gdb/Basic-Python.html) says:

> If your program changes the handling of these signals, GDB will most
likely stop working correctly.

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

Regards,
Alexey

  reply	other threads:[~2022-11-09 20:40 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 [this message]
2022-12-20 20:24     ` Tom Tromey
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=6ffe1d07cf0a8dc0b455729d8a3cb9fa66c1f2fe.camel@espressif.com \
    --to=alexey.lapshin@espressif.com \
    --cc=alexey.gerenkov@espressif.com \
    --cc=anton.maklakov@espressif.com \
    --cc=gdb-patches@sourceware.org \
    --cc=ivan@espressif.com \
    --cc=tom@tromey.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).