Home | History | Annotate | Line # | Download | only in gdb.cp
maint.exp revision 1.1 
      1 # Copyright 2003-2014 Free Software Foundation, Inc.
      2 
      3 # This program is free software; you can redistribute it and/or modify
      4 # it under the terms of the GNU General Public License as published by
      5 # the Free Software Foundation; either version 3 of the License, or
      6 # (at your option) any later version.
      7 #
      8 # This program is distributed in the hope that it will be useful,
      9 # but WITHOUT ANY WARRANTY; without even the implied warranty of
     10 # MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.  See the
     11 # GNU General Public License for more details.
     12 #
     13 # You should have received a copy of the GNU General Public License
     14 # along with this program.  If not, see <http://www.gnu.org/licenses/>.
     15 
     16 
     17 # This file tests C++-specific maintenance commands and help on those.
     18 
     19 # Currently, no source file is used.
     20 
     21 # Test the help messages.
     22 
     23 proc test_help {} {
     24     set first_component_help "Print the first class/namespace component of NAME"
     25     set namespace_help "Deprecated placeholder for removed functionality."
     26 
     27     test_prefix_command_help {"maintenance cplus"} {
     28         "C\\+\\+ maintenance commands\.\[\r\n\]+"
     29     }
     30 
     31     test_prefix_command_help {"maint cp" "maintenance cplus"} {
     32         "C\\+\\+ maintenance commands.\r\n\r\n"
     33     }
     34 
     35     set multiple_help_body "List of maintenance cplus subcommands:\r\n\r\nmaintenance cplus first_component -- ${first_component_help}\r\nmaintenance cplus namespace -- ${namespace_help}\r\n\r\nType \"help maintenance cplus\" followed by maintenance cplus subcommand name for full documentation.\r\nCommand name abbreviations are allowed if unambiguous."
     36 
     37     gdb_test "maint cp" "\"maintenance cplus\" must be followed by the name of a command.\r\n.*"
     38 
     39     gdb_test "help maint cp first_component" "${first_component_help}."
     40     gdb_test "help maint cp namespace" "${namespace_help}."
     41 }
     42 
     43 # This is used when NAME should contain only a single component.  Be
     44 # careful to make sure that parentheses get escaped properly.
     45 proc test_single_component {name} {
     46     set matchname [string_to_regexp "$name"]
     47     gdb_test "maint cp first_component $name" "$matchname"
     48 }
     49 
     50 # This is used when NAME is invalid.
     51 proc test_invalid_name {name} {
     52     set matchname [string_to_regexp "$name"]
     53     gdb_test "maint cp first_component $name" \
     54 	"During symbol reading, unexpected demangled name '$matchname'.\r\n$matchname"
     55 }
     56 
     57 proc test_first_component {} {
     58     # The function in question might complain; make sure that we see
     59     # all complaints.
     60 
     61     gdb_test_no_output "set complaints 1000"
     62 
     63     test_single_component "foo"
     64     test_single_component "operator<<"
     65     test_single_component "operator>>"
     66     test_single_component "operator ->"
     67     test_single_component "operator()"
     68     test_single_component "operator>"
     69     test_single_component "operator<"
     70     test_single_component "operator ->"
     71     test_single_component "operator  ->"
     72 
     73     test_single_component "foo()"
     74     test_single_component "foo(int)"
     75     test_single_component "foo(X::Y)"
     76     test_single_component "foo(X::Y, A::B)"
     77     test_single_component "foo(std::basic_streambuf<wchar_t,std::char_traits<wchar_t> >)"
     78     test_single_component "operator>(X::Y)"
     79 
     80     # Operator names can show up in weird places.
     81 
     82     test_single_component "int operator<< <char>()"
     83     test_single_component "T<Cooperator>"
     84 
     85     # NOTE: carlton/2003-04-23: I've only seen the first of these
     86     # produced by the demangler, but I'm including two more just to be
     87     # on the safe side.
     88     test_single_component "int foo<&(operator<<(C, C))>()"
     89     test_single_component "int foo<&operator<<(C, C)>()"
     90     test_single_component "int foo<operator<<(C, C)>()"
     91 
     92     gdb_test "maint cp first_component foo::bar" "foo"
     93     gdb_test "maint cp first_component foo::bar::baz" "foo"
     94     gdb_test "maint cp first_component C<A>::bar" "C<A>"
     95     gdb_test "maint cp first_component C<std::basic_streambuf<wchar_t,std::char_traits<wchar_t> > >::bar" "C<std::basic_streambuf<wchar_t,std::char_traits<wchar_t> > >"
     96 
     97     # Make sure we behave appropriately on invalid input.
     98 
     99     # NOTE: carlton/2003-06-25: As of today, the demangler can in fact
    100     # produce examples like the third case below: there really should
    101     # be a space between the two <'s.  See PR gdb/1245.
    102 
    103     test_invalid_name "foo<"
    104     test_invalid_name "foo("
    105     test_invalid_name "bool operator<<char>"
    106 }
    107 
    108 proc test_namespace {} {
    109     gdb_test "maint cp namespace" "The `maint namespace' command was removed."
    110 }
    111 
    112 gdb_exit
    113 gdb_start
    114 
    115 test_help
    116 test_first_component
    117 test_namespace
    118 
    119 gdb_exit
    120 return 0
    121