This is the mail archive of the
gcc-bugs@gcc.gnu.org
mailing list for the GCC project.
[Bug c++/81932] Template arguments of type unsigned generate incorrect debugging information
- From: "ryxi at stu dot xidian.edu.cn" <gcc-bugzilla at gcc dot gnu dot org>
- To: gcc-bugs at gcc dot gnu dot org
- Date: Fri, 25 Aug 2017 02:50:08 +0000
- Subject: [Bug c++/81932] Template arguments of type unsigned generate incorrect debugging information
- Auto-submitted: auto-generated
- References: <bug-81932-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=81932
--- Comment #17 from Xi Ruoyao <ryxi at stu dot xidian.edu.cn> ---
(In reply to Martin Sebor from comment #15)
> (In reply to Xi Ruoyao from comment #14)
>
> The symbols in your example are the result/ouput of demangling but the issue
> reported here is with the symbols that are input into GDB. There is more
> than one way to represent the same specialization of a template (e.g.,
> B<unsigned> and B<unsigned int>, or A<2> and A<2u>, or even A<1 + 1>). GDB
> should be able to accept all of them and recognize they all refer to the
> same specialization.
Well, then GDB would have to own a C++ name parser!
Before GDB implement this, how about generate a "secondary" debug symbol with
type suffixes, along with the "normal" one without them? It would give
backward
compatibility.