From: Kevin Buettner <kevinb@redhat.com>
To: Tom de Vries <tdevries@suse.de>
Cc: gdb-patches@sourceware.org
Subject: Re: [PATCH] [gdb/testsuite] Don't use set auto-solib-add off
Date: Sun, 9 Jun 2024 18:17:41 -0700 [thread overview]
Message-ID: <20240609181630.715ec02c@f40-zbm-amd> (raw)
In-Reply-To: <20240607144135.32128-1-tdevries@suse.de>
On Fri, 7 Jun 2024 16:41:35 +0200
Tom de Vries <tdevries@suse.de> wrote:
> In test-case gdb.mi/mi-var-child-f.exp, we have:
> ...
> mi_gdb_test "-gdb-set auto-solib-add off" "\\^done"
> mi_runto prog_array
> mi_gdb_test "nosharedlibrary" ".*\\^done"
> ...
>
> This was added to avoid a name clash between the array variable as defined in
> gdb.mi/array.f90 and debug info in shared libraries, and used in other places
> in the testsuite.
>
> The same workaround is also used to ignore symbols from shared libraries when
> excercising for instance a command that print all symbols.
>
> However, this approach can cause problems for targets like arm that require
> symbol info for some libraries like ld.so and libc to fully function.
>
> While absense of debug info for shared libraries should be handled gracefully
> (which does need fixing, see PR31817), failure to do so should not result
> in failures in unrelated test-cases.
>
> Fix this by removing "set auto-solib-add off".
>
> This ensures that we don't run into PR31817, while the presence of
> nosharedlibrary still ensures that in the rest of the test-case we're not
> bothered by shared library symbols.
>
> Likewise in other test-cases.
>
> Tested on arm-linux.
LGTM.
Approved-by: Kevin Buettner <kevinb@redhat.com>
next prev parent reply other threads:[~2024-06-10 1:18 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-06-07 14:41 Tom de Vries
2024-06-10 1:17 ` Kevin Buettner [this message]
2024-06-10 8:43 ` Tom de Vries
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=20240609181630.715ec02c@f40-zbm-amd \
--to=kevinb@redhat.com \
--cc=gdb-patches@sourceware.org \
--cc=tdevries@suse.de \
/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