From: Dmitry Neverov <dmitry.neverov@jetbrains.com>
To: Tom Tromey <tom@tromey.com>
Cc: gdb-patches@sourceware.org
Subject: Re: [RFC v2][PR symtab/30520] gdb/symtab: fix the gdb.cp/anon-struct test
Date: Mon, 18 Mar 2024 17:35:50 +0100 [thread overview]
Message-ID: <CAEY59_+6Fu+cvwGiniNip+rDXLD6-SuX9rdtqd4BLj9yxRqSmw@mail.gmail.com> (raw)
In-Reply-To: <87v86x77i1.fsf@tromey.com>
Hi Tom,
Sorry for the late reply. I was going to finish all the paperwork before
continuing, but it takes too long.
> Anyway what I was really asking is if you ran the gdb testsuite.
I've run the testsuite locally. When patch is applied I get one
additional 'KFAIL ingdb.threads/process-dies-while-handling-bp.exp'.
But this test seems to be flaky on my machine and if I rerun it in
master, it also fails.
Do you think I should fix the formatting and re-submit the
series, or is it better to wait till all papers are signed and
accepted?
Dmitry
next prev parent reply other threads:[~2024-03-18 16:36 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-01-23 17:03 [RFC v2][PR symtab/30520 1/4] gdb/symtab: check name matches before expanding a CU Dmitry Neverov
2024-01-23 17:03 ` [RFC v2][PR symtab/30520 2/4] gdb/symtab: reuse last segment lookup name info Dmitry Neverov
2024-01-23 17:03 ` [RFC v2][PR symtab/30520 3/4] gdb/symtab: compute match_type outside the loop Dmitry Neverov
2024-01-23 17:03 ` [RFC v2][PR symtab/30520 4/4] gdb/symtab: use symbol name matcher for all segments in a qualified name Dmitry Neverov
2024-01-25 8:44 ` [RFC v2][PR symtab/30520] gdb/symtab: fix the gdb.cp/anon-struct test Dmitry Neverov
2024-02-07 20:25 ` Tom Tromey
2024-02-09 16:32 ` Dmitry Neverov
2024-02-09 19:38 ` Tom Tromey
2024-03-18 16:35 ` Dmitry Neverov [this message]
2024-03-18 17:58 ` Tom Tromey
2024-03-19 12:16 ` Dmitry Neverov
2024-03-22 17:29 ` Tom Tromey
2024-05-04 1:20 ` Joel Brobecker
2024-05-06 14:32 ` Dmitry Neverov
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=CAEY59_+6Fu+cvwGiniNip+rDXLD6-SuX9rdtqd4BLj9yxRqSmw@mail.gmail.com \
--to=dmitry.neverov@jetbrains.com \
--cc=gdb-patches@sourceware.org \
--cc=tom@tromey.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