From: Pedro Alves <pedro@palves.net>
To: Tankut Baris Aktemur <tankut.baris.aktemur@intel.com>,
gdb-patches@sourceware.org
Cc: guinevere@redhat.com, eliz@gnu.org
Subject: Re: [PATCH v3 0/2] Option to show stopped threads only
Date: Thu, 24 Apr 2025 18:53:18 +0100 [thread overview]
Message-ID: <af5d92ed-d7ff-4567-9f8f-583a2414a656@palves.net> (raw)
In-Reply-To: <cover.1743772891.git.tankut.baris.aktemur@intel.com>
Hi Baris,
On 2025-04-04 14:36, Tankut Baris Aktemur wrote:
> Revision 3 makes the following changes:
...
>
> * Add a trivial "print 42" to synchronize the GDB prompt. I
> received an email notification from the Linaro CI for v2 that
> there was a test failure. Although I could not reproduce locally,
> I believe it was caused because of the buffer contents in non-stop
> mode, which is hopefully fixed now.
This usually means something is off in the test, not matching expect output
with gdb_test_multiple completely correctly, or some $gdb_prompt mishandling. I'll see if
I can fix it for you. Stay tuned.
Pedro Alves
next prev parent reply other threads:[~2025-04-24 17:53 UTC|newest]
Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-04-05 9:19 [PATCH 0/3] " Tankut Baris Aktemur via Gdb-patches
2023-04-05 9:20 ` [PATCH 1/3] gdb: pass info_threads_opts to print_thread_info_1 Tankut Baris Aktemur via Gdb-patches
2023-04-05 9:20 ` [PATCH 2/3] gdb, doc: add the missing '-gid' option to 'info threads' Tankut Baris Aktemur via Gdb-patches
2023-04-05 9:56 ` Eli Zaretskii via Gdb-patches
2023-04-05 10:12 ` Aktemur, Tankut Baris via Gdb-patches
2023-04-05 9:20 ` [PATCH 3/3] gdb: add a '-stopped' option to "info threads" Tankut Baris Aktemur via Gdb-patches
2023-04-05 10:00 ` Eli Zaretskii via Gdb-patches
2023-04-05 10:19 ` Aktemur, Tankut Baris via Gdb-patches
2023-04-05 10:50 ` Eli Zaretskii via Gdb-patches
2023-04-05 11:31 ` Aktemur, Tankut Baris via Gdb-patches
2023-04-05 11:56 ` Eli Zaretskii via Gdb-patches
2025-04-24 14:50 ` Pedro Alves
2025-03-18 18:04 ` [PATCH v2 0/2] Option to show stopped threads only Tankut Baris Aktemur
2025-03-18 18:05 ` [PATCH v2 1/2] gdb: pass info_threads_opts to print_thread_info_1 Tankut Baris Aktemur
2025-03-18 18:05 ` [PATCH v2 2/2] gdb: add a '-stopped' option to "info threads" Tankut Baris Aktemur
2025-03-28 16:38 ` [PATCH v2 0/2] Option to show stopped threads only Guinevere Larsen
2025-04-04 13:39 ` Aktemur, Tankut Baris
2025-04-04 13:36 ` [PATCH v3 " Tankut Baris Aktemur
2025-04-04 13:36 ` [PATCH v3 1/2] gdb: pass info_threads_opts to print_thread_info_1 Tankut Baris Aktemur
2025-04-24 18:09 ` Pedro Alves
2025-04-04 13:36 ` [PATCH v3 2/2] gdb: add a '-stopped' option to "info threads" Tankut Baris Aktemur
2025-04-24 19:23 ` Pedro Alves
2025-05-05 16:17 ` Aktemur, Tankut Baris
2025-04-23 8:00 ` [PATCH v3 0/2] Option to show stopped threads only Aktemur, Tankut Baris
2025-04-24 17:53 ` Pedro Alves [this message]
2025-05-05 16:19 ` [PATCH v4 0/3] Option to show stopped/running " Tankut Baris Aktemur
2025-05-05 16:19 ` [PATCH v4 1/3] gdb: pass info_threads_opts to print_thread_info_1 Tankut Baris Aktemur
2025-05-05 16:19 ` [PATCH v4 2/3] gdb: update "info threads" output when no threads match the arguments Tankut Baris Aktemur
2025-05-05 17:19 ` Eli Zaretskii
2025-05-05 16:19 ` [PATCH v4 3/3] gdb: add '-stopped' and '-running' options to "info threads" Tankut Baris Aktemur
2025-05-05 17:21 ` Eli Zaretskii
2025-05-09 20:54 ` [PATCH v4 0/3] Option to show stopped/running threads only Pedro Alves
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=af5d92ed-d7ff-4567-9f8f-583a2414a656@palves.net \
--to=pedro@palves.net \
--cc=eliz@gnu.org \
--cc=gdb-patches@sourceware.org \
--cc=guinevere@redhat.com \
--cc=tankut.baris.aktemur@intel.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