From: Pedro Alves <pedro@palves.net>
To: Lancelot SIX <lsix@lancelotsix.com>
Cc: Ulrich Weigand <Ulrich.Weigand@de.ibm.com>,
Rogerio Alves <rogealve@br.ibm.com>,
gdb-patches@sourceware.org
Subject: Re: [PATCH] Fix "b func(std::string)", use DMGL_VERBOSE (was: Re: [PATCH] Fix gdb.cp/no-dmgl-verbose.exp test)
Date: Thu, 5 May 2022 19:53:51 +0100 [thread overview]
Message-ID: <07fae3b9-0e29-234b-f530-4677edbcb3c6@palves.net> (raw)
In-Reply-To: <a4a0bb8c-0573-b99f-446b-82df56e0f058@palves.net>
On 2022-05-02 16:46, Pedro Alves wrote:
> I'll send a v2 with these fixes once I manage to write an actual commit log.
Finally found a moment to do this. I split the 'Make "b f(std::string)" even in C work' part
to a separate patch, and made it not rely on the current language. So it is now a 3 part series.
You can find it here:
[PATCH 0/3] Fix "b func(std::string)", DMGL_VERBOSE, gdb.cp/no-dmgl-verbose.exp
https://sourceware.org/pipermail/gdb-patches/2022-May/188743.html
Comments more than welcome!
next prev parent reply other threads:[~2022-05-05 18:54 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
2022-04-30 21:11 ` Lancelot SIX via Gdb-patches
2022-05-02 15:46 ` Pedro Alves
2022-05-05 18:53 ` Pedro Alves [this message]
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=07fae3b9-0e29-234b-f530-4677edbcb3c6@palves.net \
--to=pedro@palves.net \
--cc=Ulrich.Weigand@de.ibm.com \
--cc=gdb-patches@sourceware.org \
--cc=lsix@lancelotsix.com \
--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