[Bug testsuite/31632] New: [gdb/testsuite] Connecting to wrong gdbserver during parallel testing

["vries at gcc dot gnu.org" <sourceware-bugzilla@sourceware.org>]

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

            Bug ID: 31632
           Summary: [gdb/testsuite] Connecting to wrong gdbserver during
                    parallel testing
           Product: gdb
           Version: HEAD
            Status: NEW
          Severity: normal
          Priority: P2
         Component: testsuite
          Assignee: unassigned at sourceware dot org
          Reporter: vries at gcc dot gnu.org
  Target Milestone: ---

The opensuse gdb package runs the testsuite using:
...
$ make -j 16 \
  check//unix/-m64 \
  check//unix/-m64/-fPIE/-pie\
  check//unix/-m32 \
  check//unix/-m32/-fPIE/-pie
...
or alternatively with -fno-PIE/-no-pie, depending on the default.

So, AFAIU, four target boards are tested in parallel, and then each target
board is also tested in parallel.

I'm seeing (with gdb 13.2 based package) these FAILs for one target board:
...
FAIL: gdb.server/connect-without-multi-process.exp: multiprocess=off: target
remote (got interactive prompt)
FAIL: gdb.server/connect-without-multi-process.exp: multiprocess=off: continue
to main
FAIL: gdb.server/connect-without-multi-process.exp: multiprocess=off: continue
until exit
...
and these for another:
...
FAIL: gdb.server/reconnect-ctrl-c.exp: second: continue for ctrl-c (the program
is no longer running)
FAIL: gdb.server/reconnect-ctrl-c.exp: second: stop with control-c
...

Curiously, when investigating the first we see:
...
(gdb) PASS: gdb.server/connect-without-multi-process.exp: multiprocess=off:
break -q main
target remote localhost:2346^M
Remote debugging using localhost:2346^M
warning: Build ID mismatch between current exec-file
/home/abuild/rpmbuild/BUILD/gdb-13.2/build-x86_64-suse-linux/gdb/testsuite.unix.-m32.-fno-PIE.-no-pie/outputs/gdb.server/connect-without-multi-process/connect-without-multi-process^M
and automatically determined exec-file
/home/abuild/rpmbuild/BUILD/gdb-13.2/build-x86_64-suse-linux/gdb/testsuite.unix.-m32/outputs/gdb.server/reconnect-ctrl-c/reconnect-ctrl-c^M
exec-file-mismatch handling is currently "ask"^M
Load new symbol table from
"/home/abuild/rpmbuild/BUILD/gdb-13.2/build-x86_64-suse-linux/gdb/testsuite.unix.-m32/outputs/gdb.server/reconnect-ctrl-c/reconnect-ctrl-c"?
(y or n) n^M
warning: loading
/home/abuild/rpmbuild/BUILD/gdb-13.2/build-x86_64-suse-linux/gdb/testsuite.unix.-m32/outputs/gdb.server/reconnect-ctrl-c/reconnect-ctrl-c
Not confirmed.^M
warning: Could not load shared library symbols for linux-gate.so.1.^M
Do you need "set solib-search-path" or "set sysroot"?^M
Reading symbols from /lib/libc.so.6...^M
(No debugging symbols found in /lib/libc.so.6)^M
Reading symbols from /lib/ld-linux.so.2...^M
(No debugging symbols found in /lib/ld-linux.so.2)^M
0xf7fc7579 in ?? ()^M
(gdb) FAIL: gdb.server/connect-without-multi-process.exp: multiprocess=off:
target remote (got interactive prompt)
...

Looking at the other test-case, the same portnum is used.

It seems we're connecting to the wrong gdbserver.

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