2020-01-01 07:20:01 +01:00
|
|
|
# Copyright (C) 2009-2020 Free Software Foundation, Inc.
|
2009-02-14 22:58:29 +01:00
|
|
|
|
|
|
|
# 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
|
|
|
|
# the Free Software Foundation; either version 3 of the License, or
|
|
|
|
# (at your option) any later version.
|
|
|
|
#
|
|
|
|
# This program is distributed in the hope that it will be useful,
|
|
|
|
# but WITHOUT ANY WARRANTY; without even the implied warranty of
|
|
|
|
# MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the
|
|
|
|
# GNU General Public License for more details.
|
|
|
|
#
|
|
|
|
# You should have received a copy of the GNU General Public License
|
|
|
|
# along with this program. If not, see <http://www.gnu.org/licenses/>.
|
|
|
|
|
|
|
|
# This file is part of the GDB testsuite. It tests the mechanism
|
|
|
|
# for defining new GDB commands in Python.
|
|
|
|
|
2011-01-10 12:00:24 +01:00
|
|
|
load_lib gdb-python.exp
|
2009-02-14 22:58:29 +01:00
|
|
|
|
2013-11-07 13:32:31 +01:00
|
|
|
standard_testfile
|
2009-02-14 22:58:29 +01:00
|
|
|
|
2016-12-23 17:52:18 +01:00
|
|
|
if { [prepare_for_testing "failed to prepare" ${testfile} ${srcfile}] } {
|
2013-11-07 13:32:31 +01:00
|
|
|
return -1
|
|
|
|
}
|
2009-02-14 22:58:29 +01:00
|
|
|
|
2010-02-24 12:11:17 +01:00
|
|
|
# Skip all tests if Python scripting is not enabled.
|
|
|
|
if { [skip_python_tests] } { continue }
|
2009-02-14 22:58:29 +01:00
|
|
|
|
2013-11-07 13:32:31 +01:00
|
|
|
if ![runto_main] then {
|
2016-12-01 21:40:05 +01:00
|
|
|
fail "cannot run to main."
|
2013-11-07 13:32:31 +01:00
|
|
|
return 0
|
|
|
|
}
|
|
|
|
|
2009-02-14 22:58:29 +01:00
|
|
|
# Test a simple command.
|
|
|
|
|
|
|
|
gdb_py_test_multiple "input simple command" \
|
|
|
|
"python" "" \
|
|
|
|
"class test_cmd (gdb.Command):" "" \
|
|
|
|
" def __init__ (self):" "" \
|
|
|
|
" super (test_cmd, self).__init__ (\"test_cmd\", gdb.COMMAND_OBSCURE)" "" \
|
|
|
|
" def invoke (self, arg, from_tty):" "" \
|
2012-12-10 22:22:21 +01:00
|
|
|
" print (\"test_cmd output, arg = %s\" % arg)" "" \
|
2009-02-14 22:58:29 +01:00
|
|
|
"test_cmd ()" "" \
|
|
|
|
"end" ""
|
|
|
|
|
|
|
|
gdb_test "test_cmd ugh" "test_cmd output, arg = ugh" "call simple command"
|
|
|
|
|
|
|
|
# Test a prefix command, and a subcommand within it.
|
|
|
|
|
|
|
|
gdb_py_test_multiple "input prefix command" \
|
|
|
|
"python" "" \
|
|
|
|
"class prefix_cmd (gdb.Command):" "" \
|
|
|
|
" def __init__ (self):" "" \
|
|
|
|
" super (prefix_cmd, self).__init__ (\"prefix_cmd\", gdb.COMMAND_OBSCURE, gdb.COMPLETE_NONE, True)" "" \
|
|
|
|
" def invoke (self, arg, from_tty):" "" \
|
2012-12-10 22:22:21 +01:00
|
|
|
" print (\"prefix_cmd output, arg = %s\" % arg)" "" \
|
2009-02-14 22:58:29 +01:00
|
|
|
"prefix_cmd ()" "" \
|
|
|
|
"end" ""
|
|
|
|
|
|
|
|
gdb_test "prefix_cmd ugh" "prefix_cmd output, arg = ugh" "call prefix command"
|
|
|
|
|
|
|
|
gdb_py_test_multiple "input subcommand" \
|
|
|
|
"python" "" \
|
|
|
|
"class subcmd (gdb.Command):" "" \
|
|
|
|
" def __init__ (self):" "" \
|
|
|
|
" super (subcmd, self).__init__ (\"prefix_cmd subcmd\", gdb.COMMAND_OBSCURE)" "" \
|
|
|
|
" def invoke (self, arg, from_tty):" "" \
|
2012-12-10 22:22:21 +01:00
|
|
|
" print (\"subcmd output, arg = %s\" % arg)" "" \
|
2009-02-14 22:58:29 +01:00
|
|
|
"subcmd ()" "" \
|
|
|
|
"end" ""
|
|
|
|
|
|
|
|
gdb_test "prefix_cmd subcmd ugh" "subcmd output, arg = ugh" "call subcmd"
|
|
|
|
|
2009-03-21 04:13:02 +01:00
|
|
|
# Test prefix command using keyword arguments.
|
|
|
|
|
|
|
|
gdb_py_test_multiple "input prefix command, keyword arguments" \
|
|
|
|
"python" "" \
|
|
|
|
"class prefix_cmd2 (gdb.Command):" "" \
|
|
|
|
" def __init__ (self):" "" \
|
|
|
|
" super (prefix_cmd2, self).__init__ (\"prefix_cmd2\", gdb.COMMAND_OBSCURE, prefix = True, completer_class = gdb.COMPLETE_FILENAME)" "" \
|
|
|
|
" def invoke (self, arg, from_tty):" "" \
|
2012-12-10 22:22:21 +01:00
|
|
|
" print (\"prefix_cmd2 output, arg = %s\" % arg)" "" \
|
2009-03-21 04:13:02 +01:00
|
|
|
"prefix_cmd2 ()" "" \
|
|
|
|
"end" ""
|
|
|
|
|
|
|
|
gdb_test "prefix_cmd2 argh" "prefix_cmd2 output, arg = argh" "call prefix command, keyword arguments"
|
|
|
|
|
|
|
|
gdb_py_test_multiple "input subcommand under prefix_cmd2" \
|
|
|
|
"python" "" \
|
|
|
|
"class subcmd (gdb.Command):" "" \
|
|
|
|
" def __init__ (self):" "" \
|
|
|
|
" super (subcmd, self).__init__ (\"prefix_cmd2 subcmd\", gdb.COMMAND_OBSCURE)" "" \
|
|
|
|
" def invoke (self, arg, from_tty):" "" \
|
2012-12-10 22:22:21 +01:00
|
|
|
" print (\"subcmd output, arg = %s\" % arg)" "" \
|
2009-03-21 04:13:02 +01:00
|
|
|
"subcmd ()" "" \
|
|
|
|
"end" ""
|
|
|
|
|
|
|
|
gdb_test "prefix_cmd2 subcmd ugh" "subcmd output, arg = ugh" "call subcmd under prefix_cmd2"
|
|
|
|
|
2009-02-14 22:58:29 +01:00
|
|
|
# Test a subcommand in an existing GDB prefix.
|
|
|
|
|
|
|
|
gdb_py_test_multiple "input new subcommand" \
|
|
|
|
"python" "" \
|
|
|
|
"class newsubcmd (gdb.Command):" "" \
|
|
|
|
" def __init__ (self):" "" \
|
|
|
|
" super (newsubcmd, self).__init__ (\"info newsubcmd\", gdb.COMMAND_OBSCURE)" "" \
|
|
|
|
" def invoke (self, arg, from_tty):" "" \
|
2012-12-10 22:22:21 +01:00
|
|
|
" print (\"newsubcmd output, arg = %s\" % arg)" "" \
|
2009-02-14 22:58:29 +01:00
|
|
|
"newsubcmd ()" "" \
|
|
|
|
"end" ""
|
|
|
|
|
|
|
|
gdb_test "info newsubcmd ugh" "newsubcmd output, arg = ugh" "call newsubcmd"
|
2010-05-25 17:27:17 +02:00
|
|
|
|
|
|
|
# Test a command that throws gdb.GdbError.
|
|
|
|
|
|
|
|
gdb_py_test_multiple "input command to throw error" \
|
|
|
|
"python" "" \
|
|
|
|
"class test_error_cmd (gdb.Command):" "" \
|
|
|
|
" def __init__ (self):" "" \
|
|
|
|
" super (test_error_cmd, self).__init__ (\"test_error_cmd\", gdb.COMMAND_OBSCURE)" "" \
|
|
|
|
" def invoke (self, arg, from_tty):" "" \
|
|
|
|
" raise gdb.GdbError ('you lose!')" "" \
|
|
|
|
"test_error_cmd ()" "" \
|
|
|
|
"end" ""
|
|
|
|
|
|
|
|
gdb_test "test_error_cmd ugh" "you lose!" "call error command"
|
|
|
|
|
|
|
|
# Test gdb.string_to_argv.
|
|
|
|
|
2012-12-10 22:22:21 +01:00
|
|
|
gdb_test "python print (gdb.string_to_argv (\"1 2 3\"))" \
|
2010-05-25 17:27:17 +02:00
|
|
|
{\['1', '2', '3'\]} \
|
|
|
|
"string_to_argv (\"1 2 3\")"
|
|
|
|
|
2012-12-10 22:22:21 +01:00
|
|
|
gdb_test "python print (gdb.string_to_argv (\"'1 2' 3\"))" \
|
2010-05-25 17:27:17 +02:00
|
|
|
{\['1 2', '3'\]} \
|
|
|
|
"string_to_argv (\"'1 2' 3\")"
|
|
|
|
|
2012-12-10 22:22:21 +01:00
|
|
|
gdb_test "python print (gdb.string_to_argv ('\"1 2\" 3'))" \
|
2010-05-25 17:27:17 +02:00
|
|
|
{\['1 2', '3'\]} \
|
|
|
|
"string_to_argv ('\"1 2\" 3')"
|
|
|
|
|
2012-12-10 22:22:21 +01:00
|
|
|
gdb_test "python print (gdb.string_to_argv ('1\\ 2 3'))" \
|
2010-05-25 17:27:17 +02:00
|
|
|
{\['1 2', '3'\]} \
|
|
|
|
"string_to_argv ('1\\ 2 3')"
|
2012-03-01 20:30:25 +01:00
|
|
|
|
|
|
|
# Test user-defined python commands.
|
|
|
|
gdb_py_test_multiple "input simple user-defined command" \
|
|
|
|
"python" "" \
|
|
|
|
"class test_help (gdb.Command):" "" \
|
|
|
|
" \"\"\"Docstring\"\"\"" "" \
|
|
|
|
" def __init__ (self):" "" \
|
|
|
|
" super (test_help, self).__init__ (\"test_help\", gdb.COMMAND_USER)" "" \
|
|
|
|
" def invoke (self, arg, from_tty):" "" \
|
2012-12-10 22:22:21 +01:00
|
|
|
" print (\"test_cmd output, arg = %s\" % arg)" "" \
|
2012-03-01 20:30:25 +01:00
|
|
|
"test_help ()" "" \
|
|
|
|
"end" ""
|
|
|
|
|
|
|
|
gdb_test "test_help ugh" "test_cmd output, arg = ugh" "call simple user-defined command"
|
|
|
|
|
|
|
|
# Make sure the command shows up in `help user-defined`.
|
2019-06-03 21:50:22 +02:00
|
|
|
test_user_defined_class_help {"test_help -- Docstring[\r\n]"}
|
2013-11-07 13:32:31 +01:00
|
|
|
|
2014-09-08 01:12:19 +02:00
|
|
|
# Make sure the command does not show up in `show user`.
|
|
|
|
gdb_test "show user test_help" "Not a user command\." \
|
|
|
|
"don't show user-defined python command in `show user command`"
|
|
|
|
|
2013-11-07 13:32:31 +01:00
|
|
|
# Test expression completion on fields
|
|
|
|
gdb_py_test_multiple "expression completion command" \
|
|
|
|
"python" "" \
|
|
|
|
"class expr_test (gdb.Command):" "" \
|
|
|
|
" def __init__ (self):" "" \
|
|
|
|
" super (expr_test, self).__init__ (\"expr_test\", gdb.COMMAND_USER, gdb.COMPLETE_EXPRESSION)" "" \
|
|
|
|
" def invoke (self, arg, from_tty):" "" \
|
|
|
|
" print (\"invoked on = %s\" % arg)" "" \
|
|
|
|
"expr_test ()" "" \
|
|
|
|
"end" ""
|
|
|
|
|
|
|
|
|
|
|
|
gdb_test "complete expr_test bar\." \
|
|
|
|
"expr_test bar\.bc.*expr_test bar\.ij.*" \
|
2016-12-01 21:44:38 +01:00
|
|
|
"test completion through complete command"
|
2013-11-07 13:32:31 +01:00
|
|
|
|
PR cli/21688: Fix multi-line/inline command differentiation
This bug is a regression caused by the following commit:
604c4576fdcfc4e7c28f569b3748a1b6b4e0dbd4 is the first bad commit
commit 604c4576fdcfc4e7c28f569b3748a1b6b4e0dbd4
Author: Jerome Guitton <guitton@adacore.com>
Date: Tue Jan 10 15:15:53 2017 +0100
The problem happens because, on cli/cli-script.c:process_next_line,
GDB is not using the command line string to identify which command to
run, but it instead using the 'struct cmd_list_element *' that is
obtained by using the mentioned string. The problem with that is that
the 'struct cmd_list_element *' doesn't have any information on
whether the command issued by the user is a multi-line or inline one.
A multi-line command is a command that will necessarily be composed of
more than 1 line. For example:
(gdb) if 1
>python
>print ('hello')
>end
>end
As can be seen in the example above, the 'python' command actually
"opens" a new command line (represented by the change in the
indentation) that will then be used to enter Python code. OTOH, an
inline command is a command that is "self-contained" in a single line,
for example:
(gdb) if 1
>python print ('hello')
>end
This Python command is a one-liner, and therefore there is no other
Python code that can be entered for this same block. There is also no
change in the indentation.
So, the fix is somewhat simple: we have to revert the change and use
the full command line string passed to process_next_line in order to
identify whether we're dealing with a multi-line or an inline command.
This commit does just that. As can be seen, this regression also
affects other languages, like guile or the compile framework. To make
things clearer, I decided to create a new helper function responsible
for identifying a non-inline command.
Testcase is attached.
gdb/ChangeLog:
2017-06-30 Sergio Durigan Junior <sergiodj@redhat.com>
PR cli/21688
* cli/cli-script.c (command_name_equals_not_inline): New function.
(process_next_line): Adjust 'if' clauses for "python", "compile"
and "guile" to use command_name_equals_not_inline.
gdb/testsuite/ChangeLog:
2017-06-30 Sergio Durigan Junior <sergiodj@redhat.com>
PR cli/21688
* gdb.python/py-cmd.exp (test_python_inline_or_multiline): New
procedure. Call it.
2017-06-29 03:55:03 +02:00
|
|
|
# Test that the "python" command is correctly recognized as
|
|
|
|
# inline/multi-line when entering a sequence of commands.
|
|
|
|
#
|
|
|
|
# This proc tests PR cli/21688. The PR is not language-specific, but
|
|
|
|
# the easiest way is just to test with Python.
|
|
|
|
proc test_python_inline_or_multiline { } {
|
2017-06-30 14:27:29 +02:00
|
|
|
global gdb_prompt
|
2018-10-09 17:42:33 +02:00
|
|
|
set end "\r\n$gdb_prompt $"
|
2017-06-30 14:27:29 +02:00
|
|
|
|
2018-10-09 17:42:33 +02:00
|
|
|
set define_cmd_not_inline [ list \
|
|
|
|
[ list "if 1" " >$" "multi-line if 1" ] \
|
|
|
|
[ list "python" " >$" "multi-line python command" ] \
|
|
|
|
[ list "print ('hello')" " >$" "multi-line print" ] \
|
|
|
|
[ list "end" " >$" "multi-line first end" ] \
|
|
|
|
[ list "end" "hello$end" "multi-line last end" ] ]
|
PR cli/21688: Fix multi-line/inline command differentiation
This bug is a regression caused by the following commit:
604c4576fdcfc4e7c28f569b3748a1b6b4e0dbd4 is the first bad commit
commit 604c4576fdcfc4e7c28f569b3748a1b6b4e0dbd4
Author: Jerome Guitton <guitton@adacore.com>
Date: Tue Jan 10 15:15:53 2017 +0100
The problem happens because, on cli/cli-script.c:process_next_line,
GDB is not using the command line string to identify which command to
run, but it instead using the 'struct cmd_list_element *' that is
obtained by using the mentioned string. The problem with that is that
the 'struct cmd_list_element *' doesn't have any information on
whether the command issued by the user is a multi-line or inline one.
A multi-line command is a command that will necessarily be composed of
more than 1 line. For example:
(gdb) if 1
>python
>print ('hello')
>end
>end
As can be seen in the example above, the 'python' command actually
"opens" a new command line (represented by the change in the
indentation) that will then be used to enter Python code. OTOH, an
inline command is a command that is "self-contained" in a single line,
for example:
(gdb) if 1
>python print ('hello')
>end
This Python command is a one-liner, and therefore there is no other
Python code that can be entered for this same block. There is also no
change in the indentation.
So, the fix is somewhat simple: we have to revert the change and use
the full command line string passed to process_next_line in order to
identify whether we're dealing with a multi-line or an inline command.
This commit does just that. As can be seen, this regression also
affects other languages, like guile or the compile framework. To make
things clearer, I decided to create a new helper function responsible
for identifying a non-inline command.
Testcase is attached.
gdb/ChangeLog:
2017-06-30 Sergio Durigan Junior <sergiodj@redhat.com>
PR cli/21688
* cli/cli-script.c (command_name_equals_not_inline): New function.
(process_next_line): Adjust 'if' clauses for "python", "compile"
and "guile" to use command_name_equals_not_inline.
gdb/testsuite/ChangeLog:
2017-06-30 Sergio Durigan Junior <sergiodj@redhat.com>
PR cli/21688
* gdb.python/py-cmd.exp (test_python_inline_or_multiline): New
procedure. Call it.
2017-06-29 03:55:03 +02:00
|
|
|
|
2017-06-30 14:27:29 +02:00
|
|
|
# This also tests trailing whitespace on the command.
|
2018-10-09 17:42:33 +02:00
|
|
|
set define_cmd_alias_not_inline [ list \
|
|
|
|
[ list "if 1" " >$" "multi-line if 1 alias" ] \
|
|
|
|
[ list "py " " >$" "multi-line python command alias" ] \
|
|
|
|
[ list "print ('hello')" " >$" "multi-line print alias" ] \
|
|
|
|
[ list "end" " >$" "multi-line first end alias" ] \
|
|
|
|
[ list "end" "hello$end" "multi-line last end alias" ] ]
|
|
|
|
|
|
|
|
set define_cmd_alias_foo_not_inline [ list \
|
|
|
|
[ list "alias foo=python" "$end" "multi-line alias foo" ] \
|
|
|
|
[ list "if 1" " >$" "multi-line if 1 alias foo" ] \
|
|
|
|
[ list "foo " " >$" "multi-line python command alias foo" ] \
|
|
|
|
[ list "print ('hello')" " >$" "multi-line print alias foo" ] \
|
|
|
|
[ list "end" " >$" "multi-line first end alias foo" ] \
|
|
|
|
[ list "end" "hello$end" "multi-line last end alias foo" ] ]
|
|
|
|
|
|
|
|
set define_cmd_inline [ list \
|
|
|
|
[ list "if 1" " >$" "inline if 1" ] \
|
|
|
|
[ list "python print ('hello')" " >$" "inline python command" ] \
|
|
|
|
[ list "end" "hello$end" "inline end" ] ]
|
|
|
|
|
|
|
|
set define_cmd_alias_inline [ list \
|
|
|
|
[ list "if 1" " >$" "inline if 1 alias" ] \
|
|
|
|
[ list "py print ('hello')" " >$" "inline python command alias" ] \
|
|
|
|
[ list "end" "hello$end" "inline end alias" ] ]
|
|
|
|
|
|
|
|
set define_cmd_alias_foo_inline [ list \
|
|
|
|
[ list "if 1" " >$" "inline if 1 alias foo" ] \
|
|
|
|
[ list "foo print ('hello')" " >$" "inline python command alias foo" ] \
|
|
|
|
[ list "end" "hello$end" "inline end alias foo" ] ]
|
2017-06-30 14:27:29 +02:00
|
|
|
|
|
|
|
foreach t [list $define_cmd_not_inline \
|
|
|
|
$define_cmd_alias_not_inline \
|
|
|
|
$define_cmd_alias_foo_not_inline \
|
|
|
|
$define_cmd_inline \
|
|
|
|
$define_cmd_alias_inline \
|
|
|
|
$define_cmd_alias_foo_inline] {
|
PR cli/21688: Fix multi-line/inline command differentiation
This bug is a regression caused by the following commit:
604c4576fdcfc4e7c28f569b3748a1b6b4e0dbd4 is the first bad commit
commit 604c4576fdcfc4e7c28f569b3748a1b6b4e0dbd4
Author: Jerome Guitton <guitton@adacore.com>
Date: Tue Jan 10 15:15:53 2017 +0100
The problem happens because, on cli/cli-script.c:process_next_line,
GDB is not using the command line string to identify which command to
run, but it instead using the 'struct cmd_list_element *' that is
obtained by using the mentioned string. The problem with that is that
the 'struct cmd_list_element *' doesn't have any information on
whether the command issued by the user is a multi-line or inline one.
A multi-line command is a command that will necessarily be composed of
more than 1 line. For example:
(gdb) if 1
>python
>print ('hello')
>end
>end
As can be seen in the example above, the 'python' command actually
"opens" a new command line (represented by the change in the
indentation) that will then be used to enter Python code. OTOH, an
inline command is a command that is "self-contained" in a single line,
for example:
(gdb) if 1
>python print ('hello')
>end
This Python command is a one-liner, and therefore there is no other
Python code that can be entered for this same block. There is also no
change in the indentation.
So, the fix is somewhat simple: we have to revert the change and use
the full command line string passed to process_next_line in order to
identify whether we're dealing with a multi-line or an inline command.
This commit does just that. As can be seen, this regression also
affects other languages, like guile or the compile framework. To make
things clearer, I decided to create a new helper function responsible
for identifying a non-inline command.
Testcase is attached.
gdb/ChangeLog:
2017-06-30 Sergio Durigan Junior <sergiodj@redhat.com>
PR cli/21688
* cli/cli-script.c (command_name_equals_not_inline): New function.
(process_next_line): Adjust 'if' clauses for "python", "compile"
and "guile" to use command_name_equals_not_inline.
gdb/testsuite/ChangeLog:
2017-06-30 Sergio Durigan Junior <sergiodj@redhat.com>
PR cli/21688
* gdb.python/py-cmd.exp (test_python_inline_or_multiline): New
procedure. Call it.
2017-06-29 03:55:03 +02:00
|
|
|
foreach l $t {
|
|
|
|
lassign $l command regex testmsg
|
|
|
|
gdb_test_multiple "$command" "$testmsg" {
|
|
|
|
-re "$regex" {
|
|
|
|
pass "$testmsg"
|
|
|
|
}
|
|
|
|
}
|
|
|
|
}
|
|
|
|
}
|
|
|
|
}
|
|
|
|
|
|
|
|
test_python_inline_or_multiline
|
|
|
|
|
2014-03-19 03:16:35 +01:00
|
|
|
if { [readline_is_used] } {
|
|
|
|
set test "complete 'expr_test bar.i'"
|
|
|
|
send_gdb "expr_test bar\.i\t\t"
|
|
|
|
gdb_test_multiple "" "$test" {
|
|
|
|
-re "expr_test bar\.ij \\\x07$" {
|
|
|
|
send_gdb "\n"
|
|
|
|
gdb_test_multiple "" $test {
|
|
|
|
-re "invoked on = bar.ij.*$gdb_prompt $" {
|
|
|
|
pass "$test"
|
|
|
|
}
|
2013-11-07 13:32:31 +01:00
|
|
|
}
|
|
|
|
}
|
|
|
|
}
|
|
|
|
}
|
2018-12-25 20:38:01 +01:00
|
|
|
|
|
|
|
|
|
|
|
# Test that interrupting pagination throws a gdb quit.
|
|
|
|
gdb_test_no_output "set height 10"
|
|
|
|
|
|
|
|
gdb_py_test_multiple "input multi-line-output command" \
|
|
|
|
"python" "" \
|
|
|
|
"class test_mline (gdb.Command):" "" \
|
|
|
|
" \"\"\"Docstring\"\"\"" "" \
|
|
|
|
" def __init__ (self):" "" \
|
|
|
|
" super (test_mline, self).__init__ (\"test_multiline\", gdb.COMMAND_USER)" "" \
|
|
|
|
" def invoke (self, arg, from_tty):" "" \
|
|
|
|
" for f in range(20):" "" \
|
|
|
|
" print (\"test_multiline output\")" "" \
|
|
|
|
"test_mline ()" "" \
|
|
|
|
"end" ""
|
|
|
|
|
|
|
|
set test "verify pagination from test_multiline"
|
|
|
|
gdb_test_multiple "test_multiline" $test {
|
|
|
|
-re "--Type <RET>" {
|
|
|
|
exp_continue
|
|
|
|
}
|
|
|
|
-re " for more, q to quit" {
|
|
|
|
exp_continue
|
|
|
|
}
|
|
|
|
-re ", c to continue without paging--$" {
|
|
|
|
pass $test
|
|
|
|
}
|
|
|
|
}
|
|
|
|
|
|
|
|
send_gdb "q\n"
|
|
|
|
set test "verify pagination from test_multiline: q"
|
|
|
|
gdb_test_multiple "test_multiline" $test {
|
|
|
|
-re "Error occurred in Python" {
|
|
|
|
fail $test
|
|
|
|
}
|
|
|
|
-re "Quit" {
|
|
|
|
pass $test
|
|
|
|
}
|
|
|
|
}
|