State-Changed-From-To: open->suspended State-Changed-Why: We don't know if it's a bug, and the only reason the code in question isn't obsolete is that nobody has taken the time to do so.
[Converted from Gnats 945] 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). Release: GNU gdb 2002-10-11-cvs Environment: any How-To-Repeat: (gdb) set demangle-style lucid (gdb) maint demangle __vtbl__3foo__vt_cc_main_ Can't demangle "__vtbl__3foo__vt_cc_main_"
From: carlton@sources.redhat.com To: gdb-gnats@sourceware.org Cc: Subject: c++/945 Date: 17 Jan 2003 20:24:53 -0000 CVSROOT: /cvs/src Module name: src Changes by: carlton@sourceware.org 2003-01-17 12:24:52 Modified files: gdb/testsuite : ChangeLog gdb/testsuite/gdb.c++: demangle.exp Log message: 2003-01-17 David Carlton <carlton@math.stanford.edu> * gdb.c++/demangle.exp (test_lucid_style_demangling): KFAIL test corresponding to PR c++/945. Update copyright. Patches: http://sources.redhat.com/cgi-bin/cvsweb.cgi/src/gdb/testsuite/ChangeLog.diff?cvsroot=src&r1=1.465&r2=1.466 http://sources.redhat.com/cgi-bin/cvsweb.cgi/src/gdb/testsuite/gdb.c++/demangle.exp.diff?cvsroot=src&r1=1.2&r2=1.3
The bug still happens here. However, I am closing it as OBSOLETE because of the comments. Feel free to reopen if it is still an issue.