From: Tom Tromey <tom@tromey.com>
To: Pedro Alves <pedro@palves.net>
Cc: gdb-patches@sourceware.org
Subject: Re: [PATCH] testsuite: Introduce gdb_watchdog (avoid unistd.h/alarm)
Date: Tue, 12 Aug 2025 08:41:50 -0600 [thread overview]
Message-ID: <87tt2cob4h.fsf@tromey.com> (raw)
In-Reply-To: <20250808225050.1761370-1-pedro@palves.net> (Pedro Alves's message of "Fri, 8 Aug 2025 23:50:50 +0100")
>>>>> "Pedro" == Pedro Alves <pedro@palves.net> writes:
Pedro> Handle this by adding a new testsuite/lib/gdb_watchdog.h header that
Pedro> defines a new gdb_watchdog function, which wraps alarm on Unix-like
Pedro> systems, and uses a timer on Windows.
It seems like this would need some special work to handle the remote
host testing case.
Pedro> +#include "../lib/gdb_watchdog.h"
... at least, I assume this isn't automatically copied to the remote.
Tom
next prev parent reply other threads:[~2025-08-12 14:42 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-08-08 22:50 Pedro Alves
2025-08-10 3:28 ` Kevin Buettner
2025-08-11 11:48 ` Pedro Alves
2025-08-12 14:41 ` Tom Tromey [this message]
2025-08-12 18:57 ` Pedro Alves
2025-08-13 0:51 ` [PATCH v2] " Pedro Alves
2025-08-22 19:08 ` 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=87tt2cob4h.fsf@tromey.com \
--to=tom@tromey.com \
--cc=gdb-patches@sourceware.org \
--cc=pedro@palves.net \
/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