From: Carl Love <cel@us.ibm.com>
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 gdb.cp/no-dmgl-verbose.exp test
Date: Fri, 29 Apr 2022 12:13:45 -0700 [thread overview]
Message-ID: <117e54956e10755d19aeff2936600dfb89f3b1cf.camel@us.ibm.com> (raw)
In-Reply-To: <f30863e6-c591-1374-7db1-5e4f3b33ad31@palves.net>
GDB maintaners, Pedro, Lancelot:
I am not much of a C++ programer. I will have to admit that there is a
fair bit of the deep C++ behaviour with old/new APIs in Pedro's post
that is beyond me. :-) Sorry. Additionally, there is concern that
the name of the test is not accurate, etc.
So at this point, not sure where to go with fixing this test. I seem
to have opened a real can of worms. Suggestions on how to move
forward, remove the test, go with a minimal change to get the test to
pass, do a rewrite/name change, .... ?
Carl Love
next prev parent reply other threads:[~2022-04-29 19:15 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-04-29 1:28 Carl Love
2022-04-29 9:14 ` Lancelot SIX
2022-04-29 15:48 ` Carl Love
2022-04-29 16:45 ` Bruno Larsen
2022-04-29 16:57 ` Pedro Alves
2022-04-29 17:09 ` Keith Seitz
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 [this message]
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
2022-04-30 21:11 ` Lancelot SIX
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
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=117e54956e10755d19aeff2936600dfb89f3b1cf.camel@us.ibm.com \
--to=cel@us.ibm.com \
--cc=Ulrich.Weigand@de.ibm.com \
--cc=gdb-patches@sourceware.org \
--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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).