Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Ulrich Weigand <Ulrich.Weigand@de.ibm.com>
To: "akamath996@gmail.com" <akamath996@gmail.com>,
	"tom@tromey.com" <tom@tromey.com>,
	Aditya Kamath <Aditya.Kamath1@ibm.com>
Cc: "gdb-patches@sourceware.org" <gdb-patches@sourceware.org>,
	SANGAMESH MALLAYYA <sangamesh.swamy@in.ibm.com>,
	PRAJWAL B MEHENDARKAR <PRAJWAL.B.MEHENDARKAR@ibm.com>,
	"simon.marchi@polymtl.ca" <simon.marchi@polymtl.ca>
Subject: Re: [PATCH v5] Fix crash in AIX when current working directory is NULL
Date: Mon, 27 Jul 2026 12:02:20 +0000	[thread overview]
Message-ID: <3abfb7a68ab3339821acfe58adbb7a5ebb7344c1.camel@de.ibm.com> (raw)
In-Reply-To: <LV8PR15MB6488C918DB3732AB272DF2C5D6CC2@LV8PR15MB6488.namprd15.prod.outlook.com>

Aditya Kamath <Aditya.Kamath1@ibm.com> wrote:

>This is the issue. We need to find a way to mimic someone deleting the
>cwd from another terminal in one test case. In the .exp file from what
>I know we cannot find a way to delete the current working directory
>and still start GDB from the deleted directory. Let me know if I am
>wrong here.

It seems to me this is special enough that there is no particular
point in attempting to run this test in remote (or any non-default)
scenarios.  However, we would still need to prevent the test from
being *attempted* in those scenarios.  That should be possible by
using appropriate "require" lines, in particular

require isnative
require ![is_remote target]
require {istarget *-*-aix*}

The last line may be too strict if we also want to test on Linux
or other Unix hosts; but we need to ensure the host is at least
Unixy enough to support fork.  Maybe something like

require allow_fork_tests

would be OK (given that we also require isnative).

Bye,
Ulrich

  reply	other threads:[~2026-07-27 12:03 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-07-23  7:21 Aditya Vidyadhar Kamath
2026-07-24 13:25 ` Tom Tromey
2026-07-27  6:48   ` Aditya Kamath
2026-07-27 12:02     ` Ulrich Weigand [this message]
2026-07-28  7:00       ` Aditya Kamath
2026-07-28 10:09         ` Ulrich Weigand
2026-07-28 12:35           ` Aditya Kamath

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=3abfb7a68ab3339821acfe58adbb7a5ebb7344c1.camel@de.ibm.com \
    --to=ulrich.weigand@de.ibm.com \
    --cc=Aditya.Kamath1@ibm.com \
    --cc=PRAJWAL.B.MEHENDARKAR@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