Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Aditya Kamath <Aditya.Kamath1@ibm.com>
To: Simon Marchi <simon.marchi@polymtl.ca>,
	Aditya Vidyadhar Kamath <akamath996@gmail.com>,
	Ulrich Weigand <Ulrich.Weigand@de.ibm.com>,
	"tom@tromey.com" <tom@tromey.com>
Cc: "gdb-patches@sourceware.org" <gdb-patches@sourceware.org>,
	SANGAMESH MALLAYYA <sangamesh.swamy@in.ibm.com>
Subject: RE: [PATCH v2] Accept ksh88 exit status for SIGINT in shell.exp
Date: Thu, 22 Oct 2026 06:41:59 +0000	[thread overview]
Message-ID: <DSWPR15MB31981741361EE3D0C187652954D6652@DSWPR15MB319817.namprd15.prod.outlook.com> (raw)
In-Reply-To: <a5285a92-60ca-4f3b-a440-ea0c4a9f0ba5@polymtl.ca>

[-- Attachment #1: Type: text/plain, Size: 1206 bytes --]

Hi Simon and community members,

>I like the idea of testing the actual shell's behavior to set our
>expectations for what GDB should output.  There are just two
>problems:

 >- Your check uses TCL's exec, which runs on the build machine.  That
>   wouldn't be right in a remote-host scenario.  I think we can restrict
>  your check to when running with a local host.  This assumes that you
>  are not doing remote-host testing with AIX.

I missed thinking about this. Thanks. Sending a v3 version of this patch which addresses this.

> - The shell and pipe commands don't necessary use the same shell.  The
>  shell command reads the SHELL env var, but the pipe command uses
>  popen, which is hardcoded to use /bin/sh.  I presume that if you run
>   your patch with bash as your shell, you'd see a failure for the pipe
>  test.
> Can you test this patch, which addresses those two problems?

Yes, when I ran with bash SHELL I got 2 failures. Thanks for pointing out. I have addressed the same in v3 version of this patch.

All 3 shells ksh88, ksh93 and bash are tested and we have 125 passes.

Thanks again for pointing them out.

Have a nice day ahead.

Regards,
Aditya.


[-- Attachment #2: Type: text/html, Size: 5070 bytes --]

      reply	other threads:[~2026-10-22  6:42 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-10-21  9:11 Aditya Vidyadhar Kamath
2026-10-21 15:27 ` Simon Marchi
2026-10-22  6:41   ` Aditya Kamath [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=DSWPR15MB31981741361EE3D0C187652954D6652@DSWPR15MB319817.namprd15.prod.outlook.com \
    --to=aditya.kamath1@ibm.com \
    --cc=Ulrich.Weigand@de.ibm.com \
    --cc=akamath996@gmail.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