Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Rainer Orth <ro@CeBiTec.Uni-Bielefeld.DE>
To: Andrew Burgess <aburgess@redhat.com>
Cc: gdb-patches@sourceware.org,  Simon Marchi <simark@simark.ca>
Subject: Re: [PATCH] Reduce gdb.base/many-headers.c iterations on Solaris [PR34555]
Date: Mon, 21 Sep 2026 14:08:55 +0200	[thread overview]
Message-ID: <yddqzim957s.fsf@CeBiTec.Uni-Bielefeld.DE> (raw)
In-Reply-To: <87o6dqamov.fsf@redhat.com> (Andrew Burgess's message of "Mon, 21 Sep 2026 12:06:08 +0100")

Hi Andrew,

> Rainer Orth <ro@CeBiTec.Uni-Bielefeld.DE> writes:
>
>> As detailed in PR corefiles/34555, when reading the core file in the
>> gdb.base/many-headers.exp test, gdb consumes excessive amounts of memory
>> on Solaris.  If left unchecked, e.g. with ulimit -Sv 8388608, the test
>> will consume all available swap space.  Since Solaris doesn't do lazy
>> allocation, this will cause the system to become unusably slow.
>>
>> To avoid this, this patch reduces the iteration count by a factor of 100.
>>
>> Tested on sparcv9-sun-solaris2.11, x86_64-pc-solaris2.11, and
>> x86_64-pc-linux-gnu.
>>
>> Ok for trunk and the gdb-18 branch?
>>
>>
>> AFAICT, the issue is purely in gdb's Solaris corefile reader, which
>> seems to need a complete rewrite rather than a couple of bugfixes.
>
> Hi Rainer,
>
> How would you feel about the patch below being pushed?
>
> This skips the gdb.base/many-headers.exp test on Solaris.  This should
> prevent the memory exhaustion issues you are hitting, while not changing
> the underlying purpose of the test.

I'm perfectly fine with that as I'd already indicated when you first
suggested something similar:

	https://sourceware.org/pipermail/gdb-patches/2026-September/230180.html

Thanks for following up on this: I'm currently pretty swamped...

	Rainer

-- 
-----------------------------------------------------------------------------
Rainer Orth, Center for Biotechnology, Bielefeld University

  reply	other threads:[~2026-09-21 12:09 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-08-22 20:40 Rainer Orth
2026-09-07 14:35 ` Andrew Burgess
2026-09-08  8:39   ` Rainer Orth
2026-09-11 20:22   ` Tom Tromey
2026-09-21 11:06 ` Andrew Burgess
2026-09-21 12:08   ` Rainer Orth [this message]
2026-09-22  8:25     ` Andrew Burgess
2026-09-22  9:04       ` Rainer Orth

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=yddqzim957s.fsf@CeBiTec.Uni-Bielefeld.DE \
    --to=ro@cebitec.uni-bielefeld.de \
    --cc=aburgess@redhat.com \
    --cc=gdb-patches@sourceware.org \
    --cc=simark@simark.ca \
    /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