From: tdevries <tdevries@suse.de>
To: Tom Tromey <tromey@adacore.com>
Cc: gdb-patches@sourceware.org
Subject: Re: [PATCH] Use "maint ignore-probes" in no-libstdcxx-probe.exp
Date: Thu, 19 Jan 2023 22:03:23 +0000 [thread overview]
Message-ID: <745361076afa0335a48885e07cd91240@suse.de> (raw)
In-Reply-To: <20230119185607.1729073-1-tromey@adacore.com>
On 2023-01-19 18:56, Tom Tromey via Gdb-patches wrote:
> While looking at some test output, I saw that no-libstdcxx-probe.exp
> was not being run. However, it occurred to me that Tom de Vries' new
> "maint ignore-probes" command could be used to enable this test
> unconditionally.
> ---
Hi,
nice to see the new command being used :)
I've tried out the patch, works for me.
LGTM.
Thanks,
- Tom
> gdb/testsuite/gdb.cp/no-libstdcxx-probe.exp | 9 ++++-----
> 1 file changed, 4 insertions(+), 5 deletions(-)
>
> diff --git a/gdb/testsuite/gdb.cp/no-libstdcxx-probe.exp
> b/gdb/testsuite/gdb.cp/no-libstdcxx-probe.exp
> index b10daa638e6..752298af55d 100644
> --- a/gdb/testsuite/gdb.cp/no-libstdcxx-probe.exp
> +++ b/gdb/testsuite/gdb.cp/no-libstdcxx-probe.exp
> @@ -21,12 +21,11 @@ if {[prepare_for_testing "failed to prepare"
> $testfile $srcfile {debug c++}]} {
> return -1
> }
>
> -if {![runto_main]} {
> - return -1
> -}
> +# This tests that $_exception gives an error when the systemtap probes
> +# are not available, so simulate this by disabling them.
> +gdb_test "maint ignore-probes libstdcxx .*" ".*OBJNAME: ''"
>
> -if { [skip_libstdcxx_probe_tests] == 0 } {
> - untested "Have libstdc++ stap probe"
> +if {![runto_main]} {
> return -1
> }
prev parent reply other threads:[~2023-01-19 22:03 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-19 18:56 Tom Tromey
2023-01-19 22:03 ` tdevries [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=745361076afa0335a48885e07cd91240@suse.de \
--to=tdevries@suse.de \
--cc=gdb-patches@sourceware.org \
--cc=tromey@adacore.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).