From: Jonathan Wakely <jwakely@redhat.com>
To: Doug Evans <dje@google.com>
Cc: gcc-patches <gcc-patches@gcc.gnu.org>, libstdc++ <libstdc++@gcc.gnu.org>
Subject: Re: [PATCH] libstdc++: Fix list.cc xmethods test.
Date: Fri, 01 May 2015 17:02:00 -0000 [thread overview]
Message-ID: <20150501170250.GG3618@redhat.com> (raw)
In-Reply-To: <CAH6eHdSW7Q4SH6nMLR7scQOicEd4OR77x5BhWxTHB0mpnO80Jg@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1074 bytes --]
On 29/04/15 17:18 +0100, Jonathan Wakely wrote:
>On 29 April 2015 at 17:04, Doug Evans wrote:
>> Tested the same patch on the gcc 5.0 branch.
>> Just double checking ... ok to apply there too?
>
>Yes, OK for the branch too.
>
>> btw, the test is currently marked as unsupported by the test run.
>> I don't know what would be involved in marking it as failing instead,
>> but I noticed this happening a lot while I was working with this code.
>> I can imagine more failures going unnoticed because of this.
>
>That's due to:
>
>(*): Shared library is missing debugging information.^M
>skipping: (*): Shared library is missing debugging information.^M
>list.gdb:10: Error in sourced command file:^M
>Cannot evaluate function -- may be inlined^M
>skipping: list.gdb:10: Error in sourced command file:^M
>skipping: Cannot evaluate function -- may be inlined^M
>UNSUPPORTED: libstdc++-xmethods/list.cc
>
>But I can't say anything more useful than that.
This might be all that's needed to make it work with the new list, but
I can't test it due to the UNSUPPORTED error above.
[-- Attachment #2: patch.txt --]
[-- Type: text/x-patch, Size: 1174 bytes --]
diff --git a/libstdc++-v3/python/libstdcxx/v6/xmethods.py b/libstdc++-v3/python/libstdcxx/v6/xmethods.py
index 6db0e16..112d854 100644
--- a/libstdc++-v3/python/libstdcxx/v6/xmethods.py
+++ b/libstdc++-v3/python/libstdcxx/v6/xmethods.py
@@ -382,7 +382,8 @@ class ListMethodsMatcher(gdb.xmethod.XMethodMatcher):
def match(self, class_type, method_name):
if not re.match('^std::list<.*>$', class_type.tag):
- return None
+ if not re.match('^std::__cxx11::list<.*>$', class_type.tag):
+ return None
method = self._method_dict.get(method_name)
if method is None or not method.enabled:
return None
diff --git a/libstdc++-v3/testsuite/libstdc++-xmethods/list.cc b/libstdc++-v3/testsuite/libstdc++-xmethods/list.cc
index 050f75b..6c02de9 100644
--- a/libstdc++-v3/testsuite/libstdc++-xmethods/list.cc
+++ b/libstdc++-v3/testsuite/libstdc++-xmethods/list.cc
@@ -18,9 +18,6 @@
// with this library; see the file COPYING3. If not see
// <http://www.gnu.org/licenses/>.
-// List xmethods only recognize the non cxx11 std::list for now.
-#define _GLIBCXX_USE_CXX11_ABI 0
-
#include <list>
int
prev parent reply other threads:[~2015-05-01 17:02 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-04-27 22:33 Doug Evans
2015-04-27 22:41 ` Jonathan Wakely
2015-04-29 16:09 ` Doug Evans
2015-04-29 16:18 ` Jonathan Wakely
2015-04-29 16:33 ` Jonathan Wakely
2015-05-01 17:02 ` Jonathan Wakely [this message]
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=20150501170250.GG3618@redhat.com \
--to=jwakely@redhat.com \
--cc=dje@google.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=libstdc++@gcc.gnu.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).