This is the mail archive of the
gdb-prs@sources.redhat.com
mailing list for the GDB project.
c++/945: GDB can't demangle random Lucid stuff
- From: carlton at math dot stanford dot edu
- To: gdb-gnats at sources dot redhat dot com
- Date: 17 Jan 2003 20:13:50 -0000
- Subject: c++/945: GDB can't demangle random Lucid stuff
- Reply-to: carlton at math dot stanford dot edu
>Number: 945
>Category: c++
>Synopsis: GDB can't demangle random Lucid stuff
>Confidential: no
>Severity: non-critical
>Priority: low
>Responsible: unassigned
>State: open
>Class: sw-bug
>Submitter-Id: net
>Arrival-Date: Fri Jan 17 12:18:00 PST 2003
>Closed-Date:
>Last-Modified:
>Originator: carlton@math.stanford.edu
>Release: GNU gdb 2002-10-11-cvs
>Organization:
>Environment:
any
>Description:
The testsuite (gdb.c++/demangle.exp) alleges that
__vtbl__3foo__vt_cc_main_
is a legitimate mangled variable name under the Lucid style.
The testsuite, however, has no idea what the correct
demangling is. GDB can't demangle this.
I file this PR only so that I can KFAIL the test in
question: I will then suspend the PR, given that Lucid
demangling should be obsolete and that we don't really
know if the string in question really is a legitimate
mangled name (so it might not be a bug after all).
>How-To-Repeat:
(gdb) set demangle-style lucid
(gdb) maint demangle __vtbl__3foo__vt_cc_main_
Can't demangle "__vtbl__3foo__vt_cc_main_"
>Fix:
>Release-Note:
>Audit-Trail:
>Unformatted: