public inbox for gdb-prs@sourceware.org
help / color / mirror / Atom feed
From: "cvs-commit at gcc dot gnu.org" <sourceware-bugzilla@sourceware.org>
To: gdb-prs@sourceware.org
Subject: [Bug gdb/30933] FAIL: gdb.ada/file-then-restart.exp: scenario=kill: start second (the program exited) [native-gdbserver]
Date: Thu, 12 Oct 2023 13:45:11 +0000 [thread overview]
Message-ID: <bug-30933-4717-PWR16qRiAe@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-30933-4717@http.sourceware.org/bugzilla/>
https://sourceware.org/bugzilla/show_bug.cgi?id=30933
--- Comment #2 from cvs-commit at gcc dot gnu.org <cvs-commit at gcc dot gnu.org> ---
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>
--
You are receiving this mail because:
You are on the CC list for the bug.
next prev parent reply other threads:[~2023-10-12 13:45 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-10-02 18:41 [Bug gdb/30933] New: " simon.marchi at polymtl dot ca
2023-10-02 18:41 ` [Bug gdb/30933] " simon.marchi at polymtl dot ca
2023-10-04 12:44 ` tromey at sourceware dot org
2023-10-11 16:22 ` tromey at sourceware dot org
2023-10-12 13:45 ` cvs-commit at gcc dot gnu.org [this message]
2023-10-12 13:50 ` tromey at sourceware dot org
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=bug-30933-4717-PWR16qRiAe@http.sourceware.org/bugzilla/ \
--to=sourceware-bugzilla@sourceware.org \
--cc=gdb-prs@sourceware.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).