From: Carl Love via Gdb-patches <gdb-patches@sourceware.org>
To: Pedro Alves <pedro@palves.net>, Keith Seitz <keiths@redhat.com>,
Lancelot SIX <lsix@lancelotsix.com>
Cc: Ulrich Weigand <Ulrich.Weigand@de.ibm.com>,
gdb-patches@sourceware.org, Rogerio Alves <rogealve@br.ibm.com>
Subject: Re: [PATCH] Fix "b func(std::string)", use DMGL_VERBOSE (was: Re: [PATCH] Fix gdb.cp/no-dmgl-verbose.exp test)
Date: Fri, 29 Apr 2022 19:54:21 -0700 [thread overview]
Message-ID: <e40a6aca857dca0b48e1721ea69baa587111a435.camel@us.ibm.com> (raw)
In-Reply-To: <06aaa8fe-6800-492b-9c01-e2fd360304fb@palves.net>
Pedro:
I think the patch may need to be re-generated. It didn't apply cleanly
to a fresh gdb tree. Specifically, the removal of the file
gdb/testsuite/gdb.cp/no-dmgl-verbose.exp complained about being
"Reversed (or previously applied)". I had to manually remove the file.
Other than that, the new test gdb/testsuite/gdb.cp/break-std-
string.exp runs. I got 18 passes on Power 10.
Carl Love
next prev parent reply other threads:[~2022-04-30 3:11 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-04-29 1:28 [PATCH] Fix gdb.cp/no-dmgl-verbose.exp test Carl Love via Gdb-patches
2022-04-29 9:14 ` Lancelot SIX via Gdb-patches
2022-04-29 15:48 ` Carl Love via Gdb-patches
2022-04-29 16:45 ` Bruno Larsen via Gdb-patches
2022-04-29 16:57 ` Pedro Alves
2022-04-29 17:09 ` Keith Seitz via Gdb-patches
2022-04-29 17:20 ` Pedro Alves
2022-04-29 17:26 ` Pedro Alves
2022-04-29 18:40 ` Pedro Alves
2022-04-29 19:13 ` Carl Love via Gdb-patches
2022-04-30 0:56 ` [PATCH] Fix "b func(std::string)", use DMGL_VERBOSE (was: Re: [PATCH] Fix gdb.cp/no-dmgl-verbose.exp test) Pedro Alves
2022-04-30 2:54 ` Carl Love via Gdb-patches [this message]
2022-04-30 21:11 ` Lancelot SIX via Gdb-patches
2022-05-02 15:46 ` Pedro Alves
2022-05-05 18:53 ` Pedro Alves
2022-04-30 1:00 ` [PATCH] Fix gdb.cp/no-dmgl-verbose.exp test Pedro Alves
2022-04-29 17:23 ` Lancelot SIX via Gdb-patches
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=e40a6aca857dca0b48e1721ea69baa587111a435.camel@us.ibm.com \
--to=gdb-patches@sourceware.org \
--cc=Ulrich.Weigand@de.ibm.com \
--cc=cel@us.ibm.com \
--cc=keiths@redhat.com \
--cc=lsix@lancelotsix.com \
--cc=pedro@palves.net \
--cc=rogealve@br.ibm.com \
/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