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/27742] FAIL: gdb.opt/inline-locals.exp: info locals above bar 2/3
Date: Mon, 19 Apr 2021 13:16:46 +0000 [thread overview]
Message-ID: <bug-27742-4717-l8vk18BJ3J@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-27742-4717@http.sourceware.org/bugzilla/>
https://sourceware.org/bugzilla/show_bug.cgi?id=27742
--- Comment #6 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=392e0bcc0e4088ff6c31ed43a6232e709bf52751
commit 392e0bcc0e4088ff6c31ed43a6232e709bf52751
Author: Tom Tromey <tromey@adacore.com>
Date: Mon Apr 19 07:16:34 2021 -0600
Fix kfail patterns in inline-locals.exp
PR gdb/27742 points out that my recent change to
print_variable_and_value caused a regression in inline-locals.exp. I
can't reproduce this, but I came up with this patch based on the
output shown in the bug.
gdb/testsuite/ChangeLog
2021-04-19 Tom Tromey <tromey@adacore.com>
PR gdb/27742:
* gdb.opt/inline-locals.exp: Update kfail patterns.
--
You are receiving this mail because:
You are on the CC list for the bug.
next prev parent reply other threads:[~2021-04-19 13:16 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-04-16 9:16 [Bug gdb/27742] New: " vries at gcc dot gnu.org
2021-04-16 10:44 ` [Bug gdb/27742] " vries at gcc dot gnu.org
2021-04-16 16:40 ` tromey at sourceware dot org
2021-04-16 18:08 ` tromey at sourceware dot org
2021-04-16 18:12 ` vries at gcc dot gnu.org
2021-04-16 19:23 ` tromey at sourceware dot org
2021-04-19 13:16 ` cvs-commit at gcc dot gnu.org [this message]
2021-04-19 13:17 ` 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-27742-4717-l8vk18BJ3J@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).