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/26532] FAIL: gdb.base/ui-redirect.exp: debugging: continue
Date: Tue, 25 Aug 2020 15:07:49 +0000 [thread overview]
Message-ID: <bug-26532-4717-UZBs9258gA@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-26532-4717@http.sourceware.org/bugzilla/>
https://sourceware.org/bugzilla/show_bug.cgi?id=26532
--- Comment #3 from cvs-commit at gcc dot gnu.org <cvs-commit at gcc dot gnu.org> ---
The master branch has been updated by Simon Marchi <simark@sourceware.org>:
https://sourceware.org/git/gitweb.cgi?p=binutils-gdb.git;h=2bc19622c9e74655151674661b77af52e1e064f8
commit 2bc19622c9e74655151674661b77af52e1e064f8
Author: Simon Marchi <simon.marchi@efficios.com>
Date: Tue Aug 25 11:06:27 2020 -0400
gdb/testsuite: fix gdb.base/ui-redirect.exp pattern (gdb/26532)
Commit 1eb8556f5a8b ("gdb: add infrun_debug_printf macro") changed the
debug output format for `set debug infrun 1`. It broke test
gdb.base/ui-redirect.exp, which I missed:
FAIL: gdb.base/ui-redirect.exp: debugging: continue
Fix it by adjusting the pattern in the test to the new reality.
gdb/testsuite/ChangeLog:
PR gdb/26532
* gdb.base/ui-redirect.exp: Update pattern.
Change-Id: Ie8a8f6675e35a0cab55109b1534b44eb51baec9d
--
You are receiving this mail because:
You are on the CC list for the bug.
next prev parent reply other threads:[~2020-08-25 15:07 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-08-25 10:28 [Bug gdb/26532] New: " vries at gcc dot gnu.org
2020-08-25 10:29 ` [Bug gdb/26532] " vries at gcc dot gnu.org
2020-08-25 10:40 ` vries at gcc dot gnu.org
2020-08-25 11:10 ` vries at gcc dot gnu.org
2020-08-25 15:07 ` cvs-commit at gcc dot gnu.org [this message]
2020-08-25 15:07 ` cvs-commit at gcc dot gnu.org
2020-08-25 15:09 ` simark at simark dot ca
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-26532-4717-UZBs9258gA@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).