[Bug gdb/30414] New: Random failure in gdb.fortran/lbound-ubound.exp

["simon.marchi at polymtl dot ca" <sourceware-bugzilla@sourceware.org>]

https://sourceware.org/bugzilla/show_bug.cgi?id=30414

            Bug ID: 30414
           Summary: Random failure in gdb.fortran/lbound-ubound.exp
           Product: gdb
           Version: HEAD
            Status: NEW
          Severity: normal
          Priority: P2
         Component: gdb
          Assignee: unassigned at sourceware dot org
          Reporter: simon.marchi at polymtl dot ca
  Target Milestone: ---

On my CI, I often see gdb.fortran/lbound-ubound.exp failing.  Here is an
excerpt from the latest instance (it was using the native-gdbserver board,
perhaps it plays a role):

...
(gdb) break 165
Breakpoint 4 at 0x555555558bd1: file
/home/jenkins/workspace/binutils-gdb_master_linuxbuild/platform/jammy-amd64/target_board/native-gd
bserver/src/binutils-gdb/gdb/testsuite/gdb.fortran/lbound-ubound.F90, line 165.
(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 ''
up
#1  0x0000555555556782 in test () at
/home/jenkins/workspace/binutils-gdb_master_linuxbuild/platform/jammy-amd64/target_board/native-gd
bserver/src/binutils-gdb/gdb/testsuite/gdb.fortran/lbound-ubound.F90:124
124       DO_TEST (neg_array)
(gdb) ERROR: failed to extract expected results for ubound
Killing process(es): 296756
monitor exit


I haven't figured out how the test can get out of the gdb_test_multiple without
a value for ubound.

-- 
You are receiving this mail because:
You are on the CC list for the bug.