Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Simon Marchi <simon.marchi@efficios.com>
To: Tom Tromey <tom@tromey.com>, Aditya Kamath <Aditya.Kamath1@ibm.com>
Cc: "gdb-patches@sourceware.org" <gdb-patches@sourceware.org>,
	Simon Marchi <simon.marchi@polymtl.ca>,
	Ulrich Weigand <Ulrich.Weigand@de.ibm.com>,
	SANGAMESH MALLAYYA <sangamesh.swamy@in.ibm.com>
Subject: Re: [PATCH 1/2] gdb: don't let SIGPIPE kill GDB in the pipe command
Date: Wed, 14 Oct 2026 08:56:48 -0400	[thread overview]
Message-ID: <6af3fb22-5ffe-4b22-a2a6-43f4d5fc7441@efficios.com> (raw)
In-Reply-To: <87ld805u84.fsf@tromey.com>

On 10/14/26 8:42 AM, Tom Tromey wrote:
>>>>>> Aditya Kamath <Aditya.Kamath1@ibm.com> writes:
> 
>> Do you think it would make sense to handle the ksh88 behaviour in a
>> separate test-suite patch, by accepting $_shell_exitcode = 130 and
>> $_shell_exitsignal = void on AIX??
> 
> I think that would be reasonable.
> 
> thanks,
> Tom

I agree, just make sure that document in the test that this specific
outcome is expected for shell ksh88 on AIX.

Simon

  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 [this message]
2026-10-14 12:46 ` Tom Tromey
2026-10-14 12:57   ` Simon Marchi

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=6af3fb22-5ffe-4b22-a2a6-43f4d5fc7441@efficios.com \
    --to=simon.marchi@efficios.com \
    --cc=Aditya.Kamath1@ibm.com \
    --cc=Ulrich.Weigand@de.ibm.com \
    --cc=gdb-patches@sourceware.org \
    --cc=sangamesh.swamy@in.ibm.com \
    --cc=simon.marchi@polymtl.ca \
    --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