[Bug testsuite/31656] New: [gdb/testsuite] Check gdb_spawn result

[Bug testsuite/31656] New: [gdb/testsuite] Check gdb_spawn result

[vries at gcc dot gnu.org]

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

            Bug ID: 31656
           Summary: [gdb/testsuite] Check gdb_spawn result
           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 noticed ( https://sourceware.org/pipermail/gdb-patches/2024-April/208304.html
) that gdb_spawn is used without checking the result in test-case
gdb.base/sigwinch-notty.exp.

I tried to find some more instances, and got:
...
$ find gdb/testsuite/ -type f | egrep -v ChangeLog | xargs egrep '^[
\t]*gdb_spawn.*[ \t]*$' 
gdb/testsuite/gdb.base/early-init-file.exp:    gdb_spawn
gdb/testsuite/gdb.base/early-init-file.exp:    gdb_spawn
gdb/testsuite/gdb.base/early-init-file.exp:    gdb_spawn
gdb/testsuite/gdb.base/warning.exp:gdb_spawn_with_cmdline_opts \
gdb/testsuite/gdb.base/sigwinch-notty.exp:    gdb_spawn
gdb/testsuite/gdb.base/attach.exp:    gdb_spawn_attach_cmdline $testpid
gdb/testsuite/gdb.base/libsegfault.exp:    gdb_spawn_with_ld_preload
$libsegfault ""
gdb/testsuite/gdb.base/libsegfault.exp:    gdb_spawn_with_ld_preload
$libsegfault "-q"
gdb/testsuite/gdb.base/readnever.exp:    gdb_spawn
...

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