[Bug testsuite/31819] New: [gdb/testsuite] ERROR: Couldn't load server-kill-python into GDB

[Bug testsuite/31819] New: [gdb/testsuite] ERROR: Couldn't load server-kill-python into GDB

[vries at gcc dot gnu.org]

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

            Bug ID: 31819
           Summary: [gdb/testsuite] ERROR: Couldn't load
                    server-kill-python into GDB
           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: ---

I ran into:
...
builtin_spawn
/home/abuild/rpmbuild/BUILD/gdb-14.2/build-x86_64-suse-linux/gdb/testsuite.unix.-m64.-fno-PIE.-no-pie/../../gdb/gdb
-nw -nx -q -iex set height 0 -iex set width 0 -iex set build-id-verbose 0
-data-directory
/home/abuild/rpmbuild/BUILD/gdb-14.2/build-x86_64-suse-linux/gdb/data-directory
-quiet -iex set height 0 -iex set width 0^M
kill^M
(gdb) kill^M
file
/home/abuild/rpmbuild/BUILD/gdb-14.2/build-x86_64-suse-linux/gdb/testsuite.unix.-m64.-fno-PIE.-no-pie/outputs/gdb.server/server-kill-python/server-kill-python^M
The program is not being run.^M
(gdb) ERROR: Couldn't load server-kill-python into GDB.
...

I think this is a regression since commit 0f077fcae0f ("[gdb/testsuite]
Simplify gdb.server/server-kill-python.exp").

Basically that commit changed the gdb spawning such that it produces a prompt,
which is not consumed explicitly.

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

[Bug testsuite/31819] [gdb/testsuite] ERROR: Couldn't load server-kill-python into GDB

[vries at gcc dot gnu.org]

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

--- Comment #1 from Tom de Vries <vries at gcc dot gnu.org> ---
https://sourceware.org/pipermail/gdb-patches/2024-May/209469.html

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

[Bug testsuite/31819] [gdb/testsuite] ERROR: Couldn't load server-kill-python into GDB

[cvs-commit at gcc dot gnu.org]

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

--- Comment #2 from Sourceware Commits <cvs-commit at gcc dot gnu.org> ---
The master branch has been updated by Tom de Vries <vries@sourceware.org>:

https://sourceware.org/git/gitweb.cgi?p=binutils-gdb.git;h=9a50e260ee1cf3b7e355371f0f4248407101795d

commit 9a50e260ee1cf3b7e355371f0f4248407101795d
Author: Tom de Vries <tdevries@suse.de>
Date:   Wed Jun 12 19:15:45 2024 +0200

    [gdb/testsuite] Fix error in gdb.server/server-kill-python.exp

    With test-case gdb.server/server-kill-python.exp, I sometimes run into:
    ...
    builtin_spawn gdb -nw -nx -q -iex set height 0 -iex set width 0 \
      -data-directory data-directory^M
    kill^M
    (gdb) kill^M
    file server-kill-python^M
    The program is not being run.^M
    (gdb) ERROR: Couldn't load server-kill-python into GDB.
    ...

    The problem is that the spawn produces a prompt, but it's not explicitly
    consumed.

    This is a regression since commit 0f077fcae0f ("[gdb/testsuite] Simplify
    gdb.server/server-kill-python.exp").

    Fix this by consuming the initial prompt.

    PR testsuite/31819
    Bug: https://sourceware.org/bugzilla/show_bug.cgi?id=31819
    Fixes: 0f077fcae0f ("[gdb/testsuite] Simplify
gdb.server/server-kill-python.exp"

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

[Bug testsuite/31819] [gdb/testsuite] ERROR: Couldn't load server-kill-python into GDB

[vries at gcc dot gnu.org]

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

Tom de Vries <vries at gcc dot gnu.org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
         Resolution|---                         |FIXED
             Status|NEW                         |RESOLVED
   Target Milestone|---                         |16.1

--- Comment #3 from Tom de Vries <vries at gcc dot gnu.org> ---
Fixed.

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