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/30414] Random failure in gdb.fortran/lbound-ubound.exp
Date: Thu, 04 May 2023 11:57:10 +0000 [thread overview]
Message-ID: <bug-30414-4717-ddwXvLYMO5@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-30414-4717@http.sourceware.org/bugzilla/>
https://sourceware.org/bugzilla/show_bug.cgi?id=30414
--- Comment #4 from Tom de Vries <vries at gcc dot gnu.org> ---
(In reply to Simon Marchi from comment #3)
> Hmm it could be. The gdb_test_multiple reads from both the GDB output and
> the inferior's output, so it is possible that there is a race here, that we
> read GDB's prompt before we read the UBOUND line.
AFAIU, comment 0 shows the race happening:
...
(gdb) continue
Continuing.
Breakpoint 2, do_test (lb=..., ub=...) at
/home/jenkins/workspace/binutils-gdb_master_linuxbuild/platform/jammy-amd64/target_board/nati
ve-gdbserver/src/binutils-gdb/gdb/testsuite/gdb.fortran/lbound-ubound.F90:45
45 print *, "" ! Test Breakpoint
(gdb) Remote debugging from host ::1, port 37496
Expected GDB Output:
LBOUND = (-8, -10)
UBOUND = (-1, -2)
APB: Run a test here
APB: Expected lbound '(-8, -10)'
APB: Expected ubound ''
...
My understanding is that we see the order in which expect reads things, and in
this snippet the prompt comes before the UBOUND line.
--
You are receiving this mail because:
You are on the CC list for the bug.
next prev parent reply other threads:[~2023-05-04 11:57 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-05-03 1:53 [Bug gdb/30414] New: " simon.marchi at polymtl dot ca
2023-05-04 8:25 ` [Bug gdb/30414] " vries at gcc dot gnu.org
2023-05-04 8:25 ` [Bug testsuite/30414] " vries at gcc dot gnu.org
2023-05-04 11:50 ` simon.marchi at polymtl dot ca
2023-05-04 11:57 ` vries at gcc dot gnu.org [this message]
2023-05-04 12:05 ` simon.marchi at polymtl dot ca
2023-05-04 15:48 ` simon.marchi at polymtl dot ca
2023-05-18 17:22 ` cvs-commit at gcc dot gnu.org
2023-05-18 17:23 ` simon.marchi at polymtl dot ca
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-30414-4717-ddwXvLYMO5@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).