From: Tom Tromey <tom@tromey.com>
To: Pedro Alves <pedro@palves.net>
Cc: gdb-patches@sourceware.org
Subject: Re: [PATCH 0/2] Rework Cygwin signal handling
Date: Wed, 21 Feb 2024 14:14:50 -0700 [thread overview]
Message-ID: <87o7c9zfhx.fsf@tromey.com> (raw)
In-Reply-To: <20240220165605.563516-1-pedro@palves.net> (Pedro Alves's message of "Tue, 20 Feb 2024 16:56:02 +0000")
>>>>> "Pedro" == Pedro Alves <pedro@palves.net> writes:
Pedro> This upstreams a couple GDB patches that Cygwin has been carrying
Pedro> downstream.
I don't know anything about Cygwin, but considering that these seem
fairly local to that code; and Jon reports their necessity; and they
remove some special handling from windows-nat.c, I'm in favor of you
putting them in.
thanks,
Tom
next prev parent reply other threads:[~2024-02-21 21:14 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-02-20 16:56 Pedro Alves
2024-02-20 16:56 ` [PATCH 1/2] Teach gdb how to unwind cygwin _sigbe and sigdelayed frames Pedro Alves
2024-02-20 16:56 ` [PATCH 2/2] Drop special way of getting inferior context after a Cygwin signal Pedro Alves
2024-02-21 13:25 ` [PATCH 0/2] Rework Cygwin signal handling Jon Turney
2024-02-23 16:24 ` Pedro Alves
2024-02-21 21:14 ` Tom Tromey [this message]
2024-02-23 16:25 ` Pedro Alves
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=87o7c9zfhx.fsf@tromey.com \
--to=tom@tromey.com \
--cc=gdb-patches@sourceware.org \
--cc=pedro@palves.net \
/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).