From: Pedro Alves <pedro@palves.net>
To: Simon Marchi <simon.marchi@efficios.com>, gdb-patches@sourceware.org
Subject: Re: [PATCH v3 1/6] gdb/testsuite: check that "info shared" and "info linker-namespaces" before running don't crash
Date: Fri, 20 Jun 2025 19:12:03 +0100 [thread overview]
Message-ID: <2755ce98-0513-4138-bea5-b6e6f035bcae@palves.net> (raw)
In-Reply-To: <20250616193443.16703-1-simon.marchi@efficios.com>
On 2025-06-16 20:32, Simon Marchi wrote:
> This patch is new in v3.
>
> While writing my solib_ops C++ification series, I broke this, and it
> didn't seem to be caught by the testsuite. Add a test for those.
>
> The exact message for "info linker-namespaces" varies depending on the
> solib_ops of the target architecture (whether ops->num_active_namespaces
> is nullptr or not). For now, just accept any message (a crash will
> still be caught). A later patch in this series will make the message
> consistent and update this test.
>
> Change-Id: I6bce2ff317447bbf321fc9cbd2d42c3dcea0c683
> ---
> gdb/testsuite/gdb.base/dlmopen-ns-ids.exp | 5 +++++
> gdb/testsuite/gdb.base/info-shared.exp | 3 +++
> 2 files changed, 8 insertions(+)
>
> diff --git a/gdb/testsuite/gdb.base/dlmopen-ns-ids.exp b/gdb/testsuite/gdb.base/dlmopen-ns-ids.exp
> index 94b4a6e50bcf..8613056a7c8b 100644
> --- a/gdb/testsuite/gdb.base/dlmopen-ns-ids.exp
> +++ b/gdb/testsuite/gdb.base/dlmopen-ns-ids.exp
> @@ -169,6 +169,11 @@ proc_with_prefix test_conv_vars {} {
> proc test_info_linker_namespaces {} {
> clean_restart $::binfile
>
> + # Check that "info linker-namespaces" while the inferior is not running
> + # doesn't crash.
> + gdb_test "info linker-namespaces" ".*" \
You can write "" instead of ".*". It'd be the same, a leading ".*" is already implied.
Otherwise LGTM.
Approved-By: Pedro Alves <pedro@palves.net>
next prev parent reply other threads:[~2025-06-20 18:41 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-06-16 19:32 Simon Marchi
2025-06-16 19:33 ` [PATCH v3 2/6] gdb/solib: fix formatting of "info linker-namespaces" error message Simon Marchi
2025-06-20 18:12 ` Pedro Alves
2025-06-26 17:35 ` Simon Marchi
2025-06-16 19:33 ` [PATCH v3 3/6] gdb/solib: add solib -> solib_ops backlink Simon Marchi
2025-06-20 18:17 ` Pedro Alves
2025-06-16 19:33 ` [PATCH v3 4/6] gdb/solib: use solib::ops for operations that concern a single solib Simon Marchi
2025-06-20 18:17 ` Pedro Alves
2025-06-16 19:33 ` [PATCH v3 5/6] gdb/progspace: add solib_ops pointer in program_space Simon Marchi
2025-06-17 19:45 ` Guinevere Larsen
2025-06-17 20:33 ` Simon Marchi
2025-06-18 11:51 ` Guinevere Larsen
2025-06-18 14:43 ` Simon Marchi
2025-06-18 15:01 ` Guinevere Larsen
2025-06-20 18:19 ` Pedro Alves
2025-06-26 17:37 ` Simon Marchi
2025-09-02 14:49 ` Tom de Vries
2025-09-02 16:05 ` Simon Marchi
2025-09-02 16:34 ` Tom de Vries
2025-06-16 19:33 ` [PATCH v3 6/6] gdb/solib: C++ify solib_ops Simon Marchi
2025-06-20 18:20 ` Pedro Alves
2025-06-26 18:04 ` Simon Marchi
2025-06-27 22:04 ` Tom de Vries
2025-06-27 22:46 ` Thiago Jung Bauermann
2025-06-28 5:25 ` Simon Marchi
2025-06-28 6:27 ` Tom de Vries
2025-06-20 18:12 ` Pedro Alves [this message]
2025-06-26 17:30 ` [PATCH v3 1/6] gdb/testsuite: check that "info shared" and "info linker-namespaces" before running don't crash Simon Marchi
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=2755ce98-0513-4138-bea5-b6e6f035bcae@palves.net \
--to=pedro@palves.net \
--cc=gdb-patches@sourceware.org \
--cc=simon.marchi@efficios.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