From: Tom Tromey <tom@tromey.com>
To: Simon Marchi <simark@simark.ca>
Cc: Tom Tromey <tom@tromey.com>, gdb-patches@sourceware.org
Subject: Re: [PATCH v2 2/8] Use gdb::byte_vector in agent_expr
Date: Thu, 29 Jun 2023 21:16:01 -0600 [thread overview]
Message-ID: <87cz1dej2m.fsf@tromey.com> (raw)
In-Reply-To: <5a23ac6b-a6d9-895d-e379-353d94220cf7@simark.ca> (Simon Marchi's message of "Fri, 23 Jun 2023 21:40:12 -0400")
Simon> Starting with this commit, I see failures in gdb.trace/entry-values.exp,
Simon> using the native-gdbserver board. I also see these failures, which are
Simon> likely related, but I haven't checked them all:
Simon> - gdb.trace/backtrace.exp
Simon> - gdb.trace/collection.exp
Simon> - gdb.trace/unavailable.exp
I have a fix for the backtrace.exp failure, but for me the other two
have failures as far back as commit 6a4058a6, the daily version bump
from June 17. (I didn't try bisecting these, just took a stab at an
older version.)
Tom
next prev parent reply other threads:[~2023-06-30 3:18 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-06-20 17:36 [PATCH v2 0/8] C++-ify and simplify agent expressions Tom Tromey
2023-06-20 17:36 ` [PATCH v2 1/8] Remove mem2hex Tom Tromey
2023-06-20 17:36 ` [PATCH v2 2/8] Use gdb::byte_vector in agent_expr Tom Tromey
2023-06-24 1:40 ` Simon Marchi via Gdb-patches
2023-06-30 3:16 ` Tom Tromey [this message]
2023-06-20 17:36 ` [PATCH v2 3/8] Use std::vector<bool> for agent_expr::reg_mask Tom Tromey
2023-06-21 16:16 ` Simon Marchi via Gdb-patches
2023-06-23 2:37 ` Tom Tromey
2023-06-20 17:36 ` [PATCH v2 4/8] Simplify agent_expr constructor Tom Tromey
2023-06-20 17:36 ` [PATCH v2 5/8] Use bool for agent_expr::tracing Tom Tromey
2023-06-20 17:36 ` [PATCH v2 6/8] Make aop_map 'static' Tom Tromey
2023-06-20 17:36 ` [PATCH v2 7/8] Remove aop_last Tom Tromey
2023-06-20 17:36 ` [PATCH v2 8/8] Use ARRAY_SIZE in ax-general.c Tom Tromey
2023-06-20 17:45 ` [PATCH v2 0/8] C++-ify and simplify agent expressions John Baldwin
2023-06-20 18:01 ` 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=87cz1dej2m.fsf@tromey.com \
--to=tom@tromey.com \
--cc=gdb-patches@sourceware.org \
--cc=simark@simark.ca \
/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