[Bug server/29253] New: [gdb, server] FAIL: gdb.server/stop-reply-no-thread.exp: to_disable=threads: continue to main (timeout)

[Bug server/29253] New: [gdb, server] FAIL: gdb.server/stop-reply-no-thread.exp: to_disable=threads: continue to main (timeout)

[vries at gcc dot gnu.org]

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

            Bug ID: 29253
           Summary: [gdb, server] FAIL:
                    gdb.server/stop-reply-no-thread.exp:
                    to_disable=threads: continue to main (timeout)
           Product: gdb
           Version: 12.1
            Status: NEW
          Severity: normal
          Priority: P2
         Component: server
          Assignee: unassigned at sourceware dot org
          Reporter: vries at gcc dot gnu.org
  Target Milestone: ---

With gdb 12.1, on OBS for openSUSE Tumbleweed with target boards unix/-m32 and
unix/-m32/-fno-PIE/-no-pie:
...
(gdb) c^M
Continuing.^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
FAIL: gdb.server/stop-reply-no-thread.exp: to_disable=threads: continue to main
(timeout)
...

The interesting bit is that this occurred in two runs, so it's not a fluke.

Unfortunately, I could not reproduce outside of OBS, even with building from
the package sources.

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

[Bug server/29253] [gdb, server] FAIL: gdb.server/stop-reply-no-thread.exp: to_disable=threads: continue to main (timeout)

[vries at gcc dot gnu.org]

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

--- Comment #1 from Tom de Vries <vries at gcc dot gnu.org> ---
Note btw that a successful run looks like:
...
Continuing.^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
^M
Breakpoint 1, main () at
/data/vries/gdb_versions/devel/src/gdb/testsuite/gdb.server/stop-reply-no-thread.c:21^M
21        return 0;^M
(gdb) PASS: gdb.server/stop-reply-no-thread.exp: to_disable=: t_nonstop=off:
continue to main
...

So at first glance, the timeout doesn't look related to the warning.

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

[Bug server/29253] [gdb, server] FAIL: gdb.server/stop-reply-no-thread.exp: to_disable=threads: continue to main (timeout)

[vries at gcc dot gnu.org]

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

--- Comment #2 from Tom de Vries <vries at gcc dot gnu.org> ---
This reproduced again in a new run, but just on one target board, not on both.  

So, perhaps it's just slow and the timeout may or may not trigger in a busy
system.

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