From: Tom Tromey <tom@tromey.com>
To: Guinevere Larsen <blarsen@redhat.com>
Cc: gdb-patches@sourceware.org
Subject: Re: [PATCH 0/2] Small fixes to run gdb.python with clang
Date: Wed, 25 Oct 2023 09:07:25 -0600 [thread overview]
Message-ID: <87zg06n3ki.fsf@tromey.com> (raw)
In-Reply-To: <20231025142410.293981-2-blarsen@redhat.com> (Guinevere Larsen's message of "Wed, 25 Oct 2023 16:24:09 +0200")
>>>>> "Guinevere" == Guinevere Larsen <blarsen@redhat.com> writes:
Guinevere> The gdb.python subdiretory currently has 3 failures on the buildbot. One
Guinevere> is an easy one-liner to fix on GDB's side - inconsistent line
Guinevere> information from clang - and the other is a known issue with clang and
Guinevere> location expressions (see:
Guinevere> https://github.com/llvm/llvm-project/issues/64390). The third issue is
Guinevere> not easy to fix, so I considered it out of scope for this series.
These look fine to me. Thank you.
Approved-By: Tom Tromey <tom@tromey.com>
Tom
next prev parent reply other threads:[~2023-10-25 15:07 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-10-25 14:24 Guinevere Larsen
2023-10-25 14:24 ` [PATCH 1/2] gdb/testsuite: fix running gdb.python/py-explore-cc " Guinevere Larsen
2023-10-25 14:24 ` [PATCH 2/2] gdb/testsuite: add a clang XFAIL to gdb.python/py-watchpoint.exp Guinevere Larsen
2023-10-25 15:07 ` Tom Tromey [this message]
2023-10-25 16:24 ` [PATCH 0/2] Small fixes to run gdb.python with clang Guinevere 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=87zg06n3ki.fsf@tromey.com \
--to=tom@tromey.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).