From: Tom Tromey <tom@tromey.com>
To: Felix Willgerodt <felix.willgerodt@intel.com>
Cc: gdb-patches@sourceware.org
Subject: Re: [PATCH 1/1] gdb, testsuite: Fix return value in gdb.base/foll-fork.exp
Date: Wed, 22 May 2024 09:24:31 -0600 [thread overview]
Message-ID: <87fru9uaxc.fsf@tromey.com> (raw)
In-Reply-To: <20240522081408.997133-1-felix.willgerodt@intel.com> (Felix Willgerodt's message of "Wed, 22 May 2024 10:14:08 +0200")
>>>>> "Felix" == Felix Willgerodt <felix.willgerodt@intel.com> writes:
Felix> The actual reason for this were some connection problems. Though the
Felix> function check_fork_catchpoints shouldn't return an empty string, especially
Felix> as it promises to always return 0 or 1. Fix that.
Thank you. This is ok.
Approved-By: Tom Tromey <tom@tromey.com>
Tom
next prev parent reply other threads:[~2024-05-22 15:24 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-05-22 8:14 Felix Willgerodt
2024-05-22 15:24 ` Tom Tromey [this message]
2024-05-23 6:23 ` Willgerodt, Felix
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=87fru9uaxc.fsf@tromey.com \
--to=tom@tromey.com \
--cc=felix.willgerodt@intel.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).