From: Alexandra Petlanova Hajkova <ahajkova@redhat.com>
To: Tom Tromey <tromey@adacore.com>
Cc: gdb-patches@sourceware.org
Subject: Re: [PATCH 2/2] Avoid FAILs in gdb.compile
Date: Tue, 24 Jan 2023 16:41:56 +0100 [thread overview]
Message-ID: <CAJVr-EPNXecHLjadeeOJaaHoFmL3HNP1yRMA0QC_b566X_qpSQ@mail.gmail.com> (raw)
In-Reply-To: <20230123220257.3773828-3-tromey@adacore.com>
[-- Attachment #1: Type: text/plain, Size: 1660 bytes --]
On Mon, Jan 23, 2023 at 11:03 PM Tom Tromey via Gdb-patches <
gdb-patches@sourceware.org> wrote:
> Many gdb.compile C++ tests fail for me on Fedora 36. I think these
> are largely bugs in the plugin, though I didn't investigate too
> deeply. Once one failure is seen, this often cascades and sometimes
> there are many timeouts.
>
> For example, this can happen:
>
> (gdb) compile code var = a->get_var ()
> warning: Could not find symbol "_ZZ9_gdb_exprP10__gdb_regsE1a" for
> compiled module "/tmp/gdbobj-0xdI6U/out2.o".
> 1 symbols were missing, cannot continue.
>
> I think this is probably a plugin bug because, IIRC, in theory these
> symbols should be exempt from a lookup via gdb.
>
> This patch arranges to catch any catastrophic failure and then simply
> exit the entire .exp file.
>
>
I think it's great, running make check looks better with this for sure
(tried on Fedora 36)
< # of expected passes 119003
< # of unexpected failures 6
---
> # of expected passes 119023
> # of unexpected failures 43
I like how you handle unknown _ZZ9_gdb_exprP10__gdb_regsE1a symbol with
UNSUPPORTED.
gdb) compile code var = a->get_var ()
warning: Could not find symbol "_ZZ9_gdb_exprP10__gdb_regsE1a" for compiled
module "/tmp/gdbobj-Fa9HOp/out2.o".
1 symbols were missing, cannot continue.
(gdb) UNSUPPORTED: gdb.compile/compile-cplus-method.exp: GCC compiler
plugin bug
testcase
/home/ahajkova/build/gdb/gdb/testsuite/../../../../binutils-gdb/gdb/testsuite/gdb.compile/compile-cplus-method.exp
completed in 1 seconds
Running
/home/ahajkova/build/gdb/gdb/testsuite/../../../../binutils-gdb/gdb/testsuite/gdb.compile/compile-cplus-namespace.exp
...
next prev parent reply other threads:[~2023-01-24 15:42 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-23 22:02 [PATCH 0/2] Suppress some FAILs Tom Tromey
2023-01-23 22:02 ` [PATCH 1/2] Don't let .gdb_history file cause failures Tom Tromey
2023-01-23 22:02 ` [PATCH 2/2] Avoid FAILs in gdb.compile Tom Tromey
2023-01-24 15:41 ` Alexandra Petlanova Hajkova [this message]
2023-02-08 17:18 ` [PATCH 0/2] Suppress some FAILs Tom Tromey
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=CAJVr-EPNXecHLjadeeOJaaHoFmL3HNP1yRMA0QC_b566X_qpSQ@mail.gmail.com \
--to=ahajkova@redhat.com \
--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).