Re: [PATCH] gdb: don't let decltype(nullptr) hide the decltype keyword

[Tom Tromey <tom@tromey.com>]

>>>>> Sing, Victoria <Victoria.Sing@amd.com> writes:

> The attached patch fixes GDB failing to parse expressions that use
> "decltype" when the program contains a type named "decltype(nullptr)",
> which is the name compilers use for std::nullptr_t in debug
> information.

> This happens because "decltype" was a normal name in C++ before C++11.
> To support older code, GDB first checks whether the program has
> something named "decltype".  If it does, GDB uses that thing instead of
> treating "decltype" as a keyword.

> That check is too loose.  In C++, GDB ignores anything in parentheses at
> the end of a name, so that "foo" finds a function "foo(int)".  Because
> of this, the check also finds the type "decltype(nullptr)", and GDB
> wrongly stops treating "decltype" as a keyword.

I wonder if we even want to have a symbol named 'decltype(nullptr)' at
all?

That is, I wonder if this oddity should be filtered out in the DWARF
reader.

Tom