This is the mail archive of the
gcc-bugs@gcc.gnu.org
mailing list for the GCC project.
[Bug libstdc++/51649] pretty printers don't handle std::__7:: namespace
- From: "tromey at gcc dot gnu.org" <gcc-bugzilla at gcc dot gnu dot org>
- To: gcc-bugs at gcc dot gnu dot org
- Date: Wed, 21 Dec 2011 18:34:47 +0000
- Subject: [Bug libstdc++/51649] pretty printers don't handle std::__7:: namespace
- Auto-submitted: auto-generated
- References: <bug-51649-4@http.gcc.gnu.org/bugzilla/>
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=51649
--- Comment #4 from Tom Tromey <tromey at gcc dot gnu.org> 2011-12-21 18:34:47 UTC ---
(In reply to comment #3)
> Tom, I assume the plan for the libstdc++ python printers is to have a
> python/libstdcxx/v7/printers.py for the libstdc++.so.7 library, right?
>
> As we have that version today when using versioned namespaces (see PR 48698) do
> you think we should have that v7 file today? Or while the only difference
> between v6 and v7 is the nested inline namespace do you think just adding
> (__7::)? to the regexes for the v6 printers is better (at least for now)?
I didn't know about --enable-symvers=gnu.
The reason I put things into a v6 namespace is just to give us options
for the future. If a v7 libstdc++ is different enough to need different
printers, this approach would let us do that -- while also letting us
have gdb sessions where different inferiors use different versions of
libstdc++.
The two sets of printers can still share code. For example, we could move
most of the code to libstdcxx/printers.py and have the v6 and v7 variants
import that.
I am not sure what the best approach is for the current situation.
What is the purpose of --enable-symvers=gnu? How different is the v7 library?
Are there other possible configurations (configure- or user-compile-time)
that affect printers that we haven't already accounted for?