public inbox for gdb-prs@sourceware.org
help / color / mirror / Atom feed
From: "vries at gcc dot gnu.org" <sourceware-bugzilla@sourceware.org>
To: gdb-prs@sourceware.org
Subject: [Bug testsuite/28617] FAIL: gdb.base/info-os.exp: get process groups (timeout)
Date: Mon, 22 Nov 2021 19:12:18 +0000 [thread overview]
Message-ID: <bug-28617-4717-dNOP1wGEdO@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-28617-4717@http.sourceware.org/bugzilla/>
https://sourceware.org/bugzilla/show_bug.cgi?id=28617
--- Comment #2 from Tom de Vries <vries at gcc dot gnu.org> ---
(In reply to Tom de Vries from comment #0)
> In more detail:
> ...
> (gdb) info os procgroups^M
> FAIL: gdb.base/info-os.exp: get process groups (timeout)
> ...
Hmm, I see the info os processes command before runs into:
...
10916 abuild /bin/shPASS: gdb.base/info-os.exp: get process list
-c if [ -f testsuite/config.status ]; then \^M
rootme=`pwd`; export rootme; \^M
rootsrc=`cd ../../gdb; pwd`; export rootsrc; \^M
...
So the list is still being generated, but a pass is already issued? How does
that happen? I don't see any '(gdb) ' in the process list that could have
triggered this.
--
You are receiving this mail because:
You are on the CC list for the bug.
next prev parent reply other threads:[~2021-11-22 19:12 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-11-22 17:55 [Bug testsuite/28617] New: " vries at gcc dot gnu.org
2021-11-22 18:56 ` [Bug testsuite/28617] " vries at gcc dot gnu.org
2021-11-22 19:12 ` vries at gcc dot gnu.org [this message]
2021-11-22 19:18 ` vries at gcc dot gnu.org
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=bug-28617-4717-dNOP1wGEdO@http.sourceware.org/bugzilla/ \
--to=sourceware-bugzilla@sourceware.org \
--cc=gdb-prs@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).