The debugger understands nested names. Namespaces go through the same paths as classes, hence the unusual use of TYPEDEFname.
id-expression
: id-expression-internals
id-expression-internals
: qualified-id
| id-or-keyword-or-typedef-name
| TWIDDLE id-or-keyword-or-typedef-name
qualified-id
: nested-name-specifier qualified-id-follower
qualified-type
: nested-name-specifier TYPEDEFname
nested-name-specifier
: CLCL
| nested-name-specifier TYPEDEFname CLCL
qualified-id-follower