From: Tom de Vries <tdevries@suse.de>
To: gdb-patches@sourceware.org
Subject: Re: [PATCH] [gdb/testsuite] Fix gdb.mi/mi-dlmopen.exp
Date: Tue, 18 Aug 2026 09:18:45 +0200 [thread overview]
Message-ID: <fa7caad6-062a-4a82-96d1-c91da5df0477@suse.de> (raw)
In-Reply-To: <20260729104546.3108523-1-tdevries@suse.de>
On 7/29/26 12:45 PM, Tom de Vries wrote:
> The mapping looks suspiciously large to me, perhaps this is a bug in glibc.
> I didn't run into this problem with two other ppc64le-linux setups, with glibc
> versions 2.40 and 2.38. But I haven't tracked it down, so I can't rule out
> the possibility that there's a gdb problem.
I've investigated this further, and came to the conclusion that the
problem is a missing backport in glibc.
I've submitted an RFC that handles this situation in gdb instead (
https://sourceware.org/pipermail/gdb-patches/2026-August/229549.html ).
Thanks,
- Tom
prev parent reply other threads:[~2026-08-18 7:19 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-07-29 10:45 Tom de Vries
2026-08-18 7:18 ` Tom de Vries [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=fa7caad6-062a-4a82-96d1-c91da5df0477@suse.de \
--to=tdevries@suse.de \
--cc=gdb-patches@sourceware.org \
/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