[Bug c++/11784] Make lookup_typename more robust in the presence of 'const' and 'volatile'

[dje at google dot com]

https://sourceware.org/bugzilla/show_bug.cgi?id=11784

dje at google dot com changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|UNCONFIRMED                 |ASSIGNED
   Last reconfirmed|                            |2015-08-12
                 CC|                            |dje at google dot com
     Ever confirmed|0                           |1

--- Comment #1 from dje at google dot com ---
Bleah. Yeah.
I wonder if we should also be watching for "class " here.

A bigger question is whether this should behave like "ptype <type>" and thus
call the expression parser instead of going straight to symbol lookup.
Or whether we should use a different function if the caller wants ptype-like
behaviour.

(gdb) pt const int
type = const int
(gdb) py print gdb.lookup_type("const int")
Traceback (most recent call last):
  File "<string>", line 1, in <module>
gdb.error: No type named const int.
Error while executing Python code.

-- 
You are receiving this mail because:
You are on the CC list for the bug.