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: "psmith at gnu dot org" <gcc-bugzilla at gcc dot gnu dot org>
- To: gcc-bugs at gcc dot gnu dot org
- Date: Fri, 25 Aug 2017 02:11:40 +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 #16 from Paul Smith <psmith at gnu dot org> ---
I'm not familiar with the implementations but I'm not sure we can expect GDB to
be able to handle this situation, at least not with any sort of efficiency.
It's already a difficult part of GDB's job, looking up types quickly. I filed
a bug a few years ago where GDB macros slowed down by over 94x (from a few
seconds to over 11 minutes) due to a symbol lookup issue: it's a very sensitive
area.
Adding more complexity to this and asking GDB to try one variation of a given
type after another until it finds one seems less than optimal.
Even if it's decided that a change does need to happen on the GDB side,
hopefully GCC will continue to generate the expected debugging symbols until
that change is made and published in GDB.