From: Andrew Burgess <aburgess@redhat.com>
To: Bruno Larsen <blarsen@redhat.com>, gdb-patches@sourceware.org
Subject: Re: [PATCH 05/11] gdb/testsuite: allow for clang style destructors on gdb.cp/m-static.exp
Date: Wed, 26 Oct 2022 14:04:33 +0100 [thread overview]
Message-ID: <875yg67n32.fsf@redhat.com> (raw)
In-Reply-To: <20221004170747.154307-7-blarsen@redhat.com>
Bruno Larsen via Gdb-patches <gdb-patches@sourceware.org> writes:
> when running gdb.cp/m-static.exp using clang, we get the following
> failures:
>
> print test1.~gnu_obj_1^M
> $6 = {void (gnu_obj_1 * const)} 0x555555555470 <gnu_obj_1::~gnu_obj_1()>^M
> (gdb) FAIL: gdb.cp/m-static.exp: simple object instance, print destructor
> ptype test1.~gnu_obj_1^M
> type = void (gnu_obj_1 * const)^M
> (gdb) FAIL: gdb.cp/m-static.exp: simple object instance, ptype destructor
> print test1.'~gnu_obj_1'^M
> $7 = {void (gnu_obj_1 * const)} 0x555555555470 <gnu_obj_1::~gnu_obj_1()>^M
> (gdb) FAIL: gdb.cp/m-static.exp: simple object instance, print quoted destructor
>
> This is because the test is expecting an extra integer parameter on the
> destructor. Looking at the debuginfo, it seems that there is nothing
> actually wrong with this output, so these tests were changed to test
> multiple possible regexps.
> ---
> gdb/testsuite/gdb.cp/m-static.exp | 36 ++++++++++++++++++++++---------
> 1 file changed, 26 insertions(+), 10 deletions(-)
>
> diff --git a/gdb/testsuite/gdb.cp/m-static.exp b/gdb/testsuite/gdb.cp/m-static.exp
> index 979de23a44f..332e1cbe1f9 100644
> --- a/gdb/testsuite/gdb.cp/m-static.exp
> +++ b/gdb/testsuite/gdb.cp/m-static.exp
> @@ -102,16 +102,32 @@ if { [is_aarch32_target] } {
> {type = void \(single_constructor \* const\)} \
> "simple object class, ptype constructor"
>
> - gdb_test "print test1.~gnu_obj_1" \
> - { = {void \(gnu_obj_1 \* const, int\)} 0x[0-9a-f]+ <gnu_obj_1::~gnu_obj_1\(\)>} \
> - "simple object instance, print destructor"
Rather than switching to gdb_test_multiple, it might be better to just
update the regexp, like:
{ = {void \(gnu_obj_1 \* const(?:, int)?\)} 0x[0-9a-f]+ <gnu_obj_1::~gnu_obj_1\(\)>}
We already use something like this (though without the '?:' modifier) in
one of the tests below, so I think there's precedent.
Thanks,
Andrew
> - gdb_test "ptype test1.~gnu_obj_1" \
> - {type = void \(gnu_obj_1 \* const, int\)} \
> - "simple object instance, ptype destructor"
> -
> - gdb_test "print test1.'~gnu_obj_1'" \
> - { = {void \(gnu_obj_1 \*( const)?, int\)} 0x[0-9a-f]+ <gnu_obj_1::~gnu_obj_1\(\)>} \
> - "simple object instance, print quoted destructor"
> + gdb_test_multiple "print test1.~gnu_obj_1" "simple object instance, print destructor" {
> + -re -wrap { = {void \(gnu_obj_1 \* const, int\)} 0x[0-9a-f]+ <gnu_obj_1::~gnu_obj_1\(\)>} {
> + pass $gdb_test_name
> + }
> + -re -wrap { = {void \(gnu_obj_1 \* const\)} 0x[0-9a-f]+ <gnu_obj_1::~gnu_obj_1\(\)>} {
> + pass $gdb_test_name
> + }
> + }
> +
> + gdb_test_multiple "ptype test1.~gnu_obj_1" "simple object instance, ptype destructor" {
> + -re -wrap {type = void \(gnu_obj_1 \* const, int\)} {
> + pass $gdb_test_name
> + }
> + -re -wrap {type = void \(gnu_obj_1 \* const\)} {
> + pass $gdb_test_name
> + }
> + }
> +
> + gdb_test_multiple "print test1.'~gnu_obj_1'" "simple object instance, print quoted destructor" {
> + -re -wrap { = {void \(gnu_obj_1 \*( const)?, int\)} 0x[0-9a-f]+ <gnu_obj_1::~gnu_obj_1\(\)>} {
> + pass $gdb_test_name
> + }
> + -re -wrap { = {void \(gnu_obj_1 \*( const)?\)} 0x[0-9a-f]+ <gnu_obj_1::~gnu_obj_1\(\)>} {
> + pass $gdb_test_name
> + }
> + }
>
> gdb_test "ptype gnu_obj_1::'~gnu_obj_1'" \
> {type = void \(gnu_obj_1 \* const\)} \
> --
> 2.37.3
next prev parent reply other threads:[~2022-10-26 13:04 UTC|newest]
Thread overview: 36+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-10-04 17:07 [PATCH 00/11] Cleanup gdb.cp tests when running with clang Bruno Larsen
2022-10-04 17:07 ` [PATCH 01/11] gdb/testsuite: ignore Non-C-typedefs for gdb.cp/class2.exp Bruno Larsen
2022-10-26 12:02 ` Andrew Burgess
2022-10-27 8:37 ` Bruno Larsen
2022-10-28 11:37 ` Andrew Burgess
2022-10-04 17:07 ` [PATCH 02/11] gdb/testsuite: enable running gdb.cp/classes.exp with clang Bruno Larsen
2022-10-26 12:19 ` Andrew Burgess
2022-10-04 17:07 ` [PATCH 03/11] gdb/testsuite: account for clang's recursive destructor calls on gdb.cp/mb-ctor.exp Bruno Larsen
2022-10-26 12:35 ` Andrew Burgess
2022-10-04 17:07 ` [PATCH 4/9] gdb/testsuite: add XFAIL to gdb.cp/derivation.exp when using clang Bruno Larsen
2022-10-04 17:09 ` Bruno Larsen
2022-10-04 17:07 ` [PATCH 04/11] " Bruno Larsen
2022-10-26 12:37 ` Andrew Burgess
2022-10-26 14:50 ` Andrew Burgess
2022-10-04 17:07 ` [PATCH 05/11] gdb/testsuite: allow for clang style destructors on gdb.cp/m-static.exp Bruno Larsen
2022-10-26 13:04 ` Andrew Burgess [this message]
2022-10-26 14:51 ` Andrew Burgess
2022-10-04 17:07 ` [PATCH 06/11] gdb/testsuite: add XFAIL to gdb.cp/ptype-flags.exp when using clang Bruno Larsen
2022-10-26 14:08 ` Andrew Burgess
2022-10-27 13:17 ` Bruno Larsen
2022-10-28 11:38 ` Andrew Burgess
2022-10-31 12:45 ` Bruno Larsen
2022-10-04 17:07 ` [PATCH 07/11] gdb/testsuite: skip gdb.cp/anon-struct.exp " Bruno Larsen
2022-10-26 14:49 ` Andrew Burgess
2022-10-27 13:46 ` Bruno Larsen
2022-10-04 17:07 ` [PATCH 08/11] gdb/testsuite: disable gdb.cp/typeid.exp " Bruno Larsen
2022-10-26 15:37 ` Andrew Burgess
2022-10-04 17:07 ` [PATCH 09/11] gdb/testsuite: fix gdb.cp/converts.exp to run with clang Bruno Larsen
2022-10-26 15:54 ` Andrew Burgess
2022-10-31 12:46 ` Bruno Larsen
2022-10-04 17:07 ` [PATCH 10/11] gdb/testsuite: remove XFAIL on gdb.cp/temargs.exp Bruno Larsen
2022-10-26 15:57 ` Andrew Burgess
2022-10-04 17:07 ` [PATCH 11/11] gdb/testsuite: disable gdb.cp/call-method-register.exp with clang Bruno Larsen
2022-10-27 9:49 ` Andrew Burgess
2022-10-31 10:51 ` Bruno Larsen
2022-10-18 8:10 ` [PING][PATCH 00/11] Cleanup gdb.cp tests when running " Bruno Larsen
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=875yg67n32.fsf@redhat.com \
--to=aburgess@redhat.com \
--cc=blarsen@redhat.com \
--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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).