From: Tom Tromey <tromey@adacore.com>
To: Luis Machado <luis.machado@arm.com>
Cc: Tom Tromey <tromey@adacore.com>,
Tom Tromey via Gdb-patches <gdb-patches@sourceware.org>
Subject: Re: [PATCH 0/3] Fix "attach" infinite loop
Date: Tue, 05 Dec 2023 12:27:56 -0700 [thread overview]
Message-ID: <87plzkjvpf.fsf@tromey.com> (raw)
In-Reply-To: <a6be03ef-9337-4693-a835-99ae5a0bc16e@arm.com> (Luis Machado's message of "Mon, 4 Dec 2023 14:25:54 +0000")
>>>>> "Luis" == Luis Machado <luis.machado@arm.com> writes:
Luis> I'm getting the following on aarch64-linux Ubuntu 22.04:
Luis> FAIL: gdb.threads/attach-many-short-lived-threads.exp: iter 1: break at break_fn: 1 (the program is no longer running)
Luis> FAIL: gdb.threads/attach-many-short-lived-threads.exp: iter 1: break at break_fn: 2 (the program is no longer running)
Luis> FAIL: gdb.threads/attach-many-short-lived-threads.exp: iter 1: break at break_fn: 3 (the program is no longer running)
Luis> FAIL: gdb.threads/attach-many-short-lived-threads.exp: iter 1: reset timer in the inferior
Luis> FAIL: gdb.threads/attach-many-short-lived-threads.exp: iter 1: detach (the program is no longer running)
I was able to reproduce this, I'll take a look.
Tom
next prev parent reply other threads:[~2023-12-05 19:27 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-10-03 17:56 Tom Tromey
2023-10-03 17:56 ` [PATCH 1/3] Minor cleanup in linux_proc_attach_tgid_threads Tom Tromey
2023-10-04 1:29 ` Simon Marchi
2023-10-03 17:56 ` [PATCH 2/3] Use gdb_dir_up " Tom Tromey
2023-10-04 1:30 ` Simon Marchi
2023-10-03 17:56 ` [PATCH 3/3] Bail out of "attach" if a thread cannot be traced Tom Tromey
2023-10-04 1:29 ` Simon Marchi
2023-10-04 14:14 ` Tom Tromey
2023-10-04 17:38 ` Simon Marchi
2023-12-01 17:41 ` [PATCH 0/3] Fix "attach" infinite loop Tom Tromey
2023-12-04 14:25 ` Luis Machado
2023-12-05 19:27 ` Tom Tromey [this message]
2023-12-15 19:33 ` Tom Tromey
2023-12-18 9:50 ` Luis Machado
2023-12-18 11:33 ` Luis Machado
2023-12-18 14:30 ` Tom Tromey
2023-12-18 15:10 ` Luis Machado
2024-01-02 19:14 ` Carl Love
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=87plzkjvpf.fsf@tromey.com \
--to=tromey@adacore.com \
--cc=gdb-patches@sourceware.org \
--cc=luis.machado@arm.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).