I see these failures when running gdb.ada/file-then-restart.exp with the native-extended-gdbserver board: FAIL: gdb.ada/file-then-restart.exp: scenario=kill: start second (the program exited) FAIL: gdb.ada/file-then-restart.exp: scenario=no-kill: start second (the program exited)
https://sourceware.org/pipermail/gdb-patches/2023-October/203163.html
The master branch has been updated by Tom Tromey <tromey@sourceware.org>: https://sourceware.org/git/gitweb.cgi?p=binutils-gdb.git;h=07c833f99c331f9eb77901cdfd143fce5acc8454 commit 07c833f99c331f9eb77901cdfd143fce5acc8454 Author: Tom Tromey <tromey@adacore.com> Date: Wed Oct 11 10:20:04 2023 -0600 Fix test suite failure in file-then-restart.exp Simon pointed out that the new file-then-restart.exp test fails with the extended-remote target board. The problem is that the test suite doesn't use gdb_file_cmd -- which handles things like "set remote exec-file". This patch changes gdb_file_cmd to make the "kill" command optional, and then switches the test case to use it. Bug: https://sourceware.org/bugzilla/show_bug.cgi?id=30933 Approved-By: Simon Marchi <simon.marchi@efficios.com>
Fixed.