Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Andrew Burgess <aburgess@redhat.com>
To: Aditya Vidyadhar Kamath <akamath996@gmail.com>,
	ulrich.weigand@de.ibm.com, simon.marchi@polymtl.ca,
	tom@tromey.com
Cc: gdb-patches@sourceware.org, Aditya.Kamath1@ibm.com,
	sangamesh.swamy@in.ibm.com,
	Aditya Vidyadhar Kamath <aditya.kamath1@ibm.com>
Subject: Re: [PATCH] Skip bigcore.exp on AIX
Date: Thu, 15 Oct 2026 15:54:28 +0100	[thread overview]
Message-ID: <87wlrj815n.fsf@redhat.com> (raw)
In-Reply-To: <20261015134700.81681-2-akamath996@gmail.com>

Aditya Vidyadhar Kamath <akamath996@gmail.com> writes:

> From: Aditya Vidyadhar Kamath <aditya.kamath1@ibm.com>
>
> AIX does not support sparse core files, so bigcore.exp, which
> allocates up to 16GB and then dumps core, is too slow and large there
> and fails.  Add AIX to the list of targets without sparse corefile

In prose 'core file' is the right choice.  I only notice because you got
this write in the first sentence :)

But otherwise:

Approved-By: Andrew Burgess <aburgess@redhat.com>

Thanks,
Andrew

> support, so that the test is reported as untested.
> ---
>  gdb/testsuite/gdb.base/bigcore.exp | 1 +
>  1 file changed, 1 insertion(+)
>
> diff --git a/gdb/testsuite/gdb.base/bigcore.exp b/gdb/testsuite/gdb.base/bigcore.exp
> index 41f61996bbe..d66706e858e 100644
> --- a/gdb/testsuite/gdb.base/bigcore.exp
> +++ b/gdb/testsuite/gdb.base/bigcore.exp
> @@ -28,6 +28,7 @@ require isnative
>  # I/O bandwidth.
>  
>  if { [istarget "*-*-*bsd*"]
> +     || [istarget "*-*-aix*"]
>       || [istarget "*-*-solaris*"]
>       || [istarget "*-*-darwin*"]
>       || [istarget "*-*-cygwin*"] } {
> -- 
> 2.51.2


  reply	other threads:[~2026-10-15 14:55 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-10-15 13:47 Aditya Vidyadhar Kamath
2026-10-15 14:54 ` Andrew Burgess [this message]
2026-10-16 10:59   ` 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=87wlrj815n.fsf@redhat.com \
    --to=aburgess@redhat.com \
    --cc=Aditya.Kamath1@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 \
    --cc=ulrich.weigand@de.ibm.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