This is the mail archive of the mailing list for the GDB project.

Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

[patch] lucid demangling XFAIL->KFAIL

The test gdb.c++/demangle.exp has what claims to be a bug in our Lucid
demangling, which is XFAILed.  I don't know if it's a bug or not; I do
know that neither I nor anybody else cares.  I've filed a PR for it,
suspended the PR (since we're not sure if it's a bug and the
demangling style should be obsoleted, anyways), and converted the

David Carlton

2003-01-17  David Carlton  <>

	* gdb.c++/demangle.exp (test_lucid_style_demangling): KFAIL test
	corresponding to PR c++/945.
	Update copyright.

Index: demangle.exp
RCS file: /cvs/src/src/gdb/testsuite/gdb.c++/demangle.exp,v
retrieving revision 1.2
diff -u -p -r1.2 demangle.exp
--- demangle.exp	13 Jan 2002 23:54:10 -0000	1.2
+++ demangle.exp	17 Jan 2003 20:23:46 -0000
@@ -1,4 +1,4 @@
-# Copyright (C) 1992, 1997, 1999 Free Software Foundation, Inc.
+# Copyright (C) 1992, 1997, 1999, 2003 Free Software Foundation, Inc.
 # This program is free software; you can redistribute it and/or modify
 # it under the terms of the GNU General Public License as published by
@@ -694,7 +694,10 @@ proc test_lucid_style_demangling {} {
     # GDB 930701 gets into an infinite loop.
     # GDB 930727 says "Can't demangle".
     # What is the correct demangling?  FIXME.
-    setup_xfail "*-*-*"
+    # NOTE: carlton/2003-01-17: No, don't FIXME, just obsolete lucid.
+    # I'm KFAILing this rather than deleting it for form's sake.
+    setup_kfail "gdb/945" "*-*-*"
     test_demangling_exact "lucid: __vtbl__3foo__vt_cc_main_" ""
     test_demangling_exact "lucid: abs__F7complex" "abs(complex)"

Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]