From: Simon Marchi <simon.marchi@polymtl.ca>
To: Tom Tromey <tom@tromey.com>, Simon Marchi <simon.marchi@efficios.com>
Cc: gdb-patches@sourceware.org
Subject: Re: [PATCH 1/2] gdb: don't let SIGPIPE kill GDB in the pipe command
Date: Wed, 14 Oct 2026 08:57:24 -0400 [thread overview]
Message-ID: <b6e9b2e5-563c-4d2c-a276-0f9d79f713af@polymtl.ca> (raw)
In-Reply-To: <87h5io5u20.fsf@tromey.com>
On 10/14/26 8:46 AM, Tom Tromey wrote:
>>>>>> "Simon" == Simon Marchi <simon.marchi@efficios.com> writes:
>
> Simon> Fix it by ignoring SIGPIPE for the duration of pipe_command, using
> Simon> scoped_ignore_sigpipe. Writes to the pipe then fail with EPIPE, which
> Simon> stdio_file ignores.
>
> Makes sense.
> Approved-By: Tom Tromey <tom@tromey.com>
>
> Tom
Thanks, pushed both.
Simon
prev parent reply other threads:[~2026-10-14 12:57 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-13 17:13 Simon Marchi
2026-10-13 17:13 ` [PATCH 2/2] gdb: preserve shell command exit status in pipe command on EPIPE Simon Marchi
2026-10-14 12:46 ` Tom Tromey
2026-10-14 9:32 ` [PATCH 1/2] gdb: don't let SIGPIPE kill GDB in the pipe command Aditya Kamath
2026-10-14 12:42 ` Tom Tromey
2026-10-14 12:56 ` Simon Marchi
2026-10-14 12:46 ` Tom Tromey
2026-10-14 12:57 ` Simon Marchi [this message]
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=b6e9b2e5-563c-4d2c-a276-0f9d79f713af@polymtl.ca \
--to=simon.marchi@polymtl.ca \
--cc=gdb-patches@sourceware.org \
--cc=simon.marchi@efficios.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