From: Tom Tromey <tom@tromey.com>
To: Tom de Vries via Gdb-patches <gdb-patches@sourceware.org>
Cc: Tom de Vries <tdevries@suse.de>
Subject: Re: [PATCH] [gdb/testsuite] Fix gdb.server/ext-run.exp in container
Date: Tue, 26 Sep 2023 07:56:03 -0600 [thread overview]
Message-ID: <874jjh598s.fsf@tromey.com> (raw)
In-Reply-To: <20230926134050.16994-1-tdevries@suse.de> (Tom de Vries via Gdb-patches's message of "Tue, 26 Sep 2023 15:40:50 +0200")
>>>>> "Tom" == Tom de Vries via Gdb-patches <gdb-patches@sourceware.org> writes:
Tom> When running the gdb testsuite inside a container, I run into:
Tom> ...
Tom> (gdb) gdb_expect_list pattern: /1 +root +[/a-z]*(init|systemd)/
Tom> FAIL: gdb.server/ext-run.exp: get process list (pattern 2)
Tom> ...
Tom> because there's no process with pid 1 and cmd init or systemd.
...
Tom> Fix this by also accepting bash as a valid cmd.
This seems totally fine to me, since IIUC the precise image here doesn't
matter at all to the test.
Approved-By: Tom Tromey <tom@tromey.com>
Tom
prev parent reply other threads:[~2023-09-26 13:56 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-09-26 13:40 Tom de Vries
2023-09-26 13:56 ` Tom Tromey [this message]
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=874jjh598s.fsf@tromey.com \
--to=tom@tromey.com \
--cc=gdb-patches@sourceware.org \
--cc=tdevries@suse.de \
/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).