From: Carl Love via Gdb-patches <gdb-patches@sourceware.org>
To: Pedro Alves <pedro@palves.net>, gdb-patches@sourceware.org
Subject: Re: [PATCH 1/3] Fix "b f(std::string)", always use DMGL_VERBOSE
Date: Thu, 05 May 2022 14:49:34 -0700 [thread overview]
Message-ID: <c5e6432093cd1008cec4115c9f8dad300f5a4a5c.camel@us.ibm.com> (raw)
In-Reply-To: <20220505185020.3648774-2-pedro@palves.net>
Pedro:
I pulled down a fresh copy of gdb and tried to apply the first patch.
There were issues with patching the files:
patch -p 1 < Fix__b_f_std_string__,_always_use_DMGL_VERBOSE_1.patch
(Stripping trailing CRs from patch; use --binary to disable.)
patching file gdb/cp-name-parser.y
(Stripping trailing CRs from patch; use --binary to disable.)
patching file gdb/cp-support.c
(Stripping trailing CRs from patch; use --binary to disable.)
patching file gdb/cp-support.h
patching file gdb/testsuite/gdb.cp/break-f-std-string.cc (renamed from
gdb/testsuite/gdb.cp/no-dmgl-verbose.cc)
(Stripping trailing CRs from patch; use --binary to disable.)
patching file gdb/testsuite/gdb.cp/break-f-std-string.exp
(Stripping trailing CRs from patch; use --binary to disable.)
patching file gdb/testsuite/gdb.cp/no-dmgl-verbose.exp
Reversed (or previously applied) patch detected! Assume -R? [n] n
Apply anyway? [n] n
Skipping patch.
1 out of 1 hunk ignored -- saving rejects to file
gdb/testsuite/gdb.cp/no-dmgl-verbose.exp.rej
The issue seems to be with deleting the file:
gdb/testsuite/gdb.cp/no-dmgl-verbose.exp
I manually deleted it. I then used git to commit the patch to my local
git directory so I could add the second patch.
The second patch applied cleanly.
The third patch applied cleanly.
I ran the test gdb.cp/break-f-std-string.exp. It runs without errors
on a Power 10 system.
testcase gdb/testsuite/gdb.cp/break-f-std-string.exp completed in 1
seconds
=== gdb Summary ===
# of expected passes 16
I also ran the full regression suite with and without the patch. No
regression failures were found.
Other than the patch not cleanly removing gdb/testsuite/gdb.cp/no-dmgl-
verbose.exp it all looks good.
Thanks for fixing this test.
Carl Love
next prev parent reply other threads:[~2022-05-05 21:50 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-05-05 18:50 [PATCH 0/3] Fix "b func(std::string)", DMGL_VERBOSE, gdb.cp/no-dmgl-verbose.exp Pedro Alves
2022-05-05 18:50 ` [PATCH 1/3] Fix "b f(std::string)", always use DMGL_VERBOSE Pedro Alves
2022-05-05 20:31 ` Keith Seitz via Gdb-patches
2022-05-05 21:49 ` Carl Love via Gdb-patches [this message]
2022-05-06 13:21 ` Pedro Alves
2022-05-06 8:10 ` Lancelot SIX via Gdb-patches
2022-05-06 13:09 ` Pedro Alves
2022-05-05 18:50 ` [PATCH 2/3] Always pass an explicit language down to c_type_print Pedro Alves
2022-05-05 20:47 ` Keith Seitz via Gdb-patches
2022-05-06 12:33 ` Pedro Alves
2022-05-05 18:50 ` [PATCH 3/3] Fix "b f(std::string)" when current language is C Pedro Alves
2022-05-05 20:50 ` Keith Seitz via Gdb-patches
2022-05-06 8:34 ` Lancelot SIX via Gdb-patches
2022-05-06 13:09 ` Pedro Alves
2022-05-09 16:54 ` [PATCH 0/3] Fix "b func(std::string)", DMGL_VERBOSE, gdb.cp/no-dmgl-verbose.exp Tom Tromey
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=c5e6432093cd1008cec4115c9f8dad300f5a4a5c.camel@us.ibm.com \
--to=gdb-patches@sourceware.org \
--cc=cel@us.ibm.com \
--cc=pedro@palves.net \
/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