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

["andre dot poenitz at nokia dot com" <sourceware-bugzilla at sourceware dot org>]

The code
          {
            if (!strncmp (type_name, "struct ", 7))
              type = lookup_struct (type_name + 7, NULL);
            else if (!strncmp (type_name, "union ", 6))
              type = lookup_union (type_name + 6, NULL);
            else if (!strncmp (type_name, "enum ", 5))
              type = lookup_enum (type_name + 5, NULL);
            else
              type = lookup_typename (python_language, python_gdbarch,
                                      type_name, block, 0);
          }

fails to remove the "human readable bits" in the presence of 'const' and
'volatile' as in 'const struct foo'.

-- 
           Summary: Make lookup_typename more robust in the presence of
                    'const' and 'volatile'
           Product: gdb
           Version: 7.1
            Status: UNCONFIRMED
          Severity: normal
          Priority: P2
         Component: c++
        AssignedTo: unassigned at sourceware dot org
        ReportedBy: andre dot poenitz at nokia dot com
                CC: gdb-prs at sourceware dot org
 GCC build triplet: i486-linux-gnu
  GCC host triplet: i486-linux-gnu
GCC target triplet: i486-linux-gnu


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

------- You are receiving this mail because: -------
You are on the CC list for the bug, or are watching someone who is.