diff options
author | Simon Marchi <simon.marchi@polymtl.ca> | 2022-08-16 10:41:47 -0400 |
---|---|---|
committer | Simon Marchi <simon.marchi@polymtl.ca> | 2022-08-16 10:43:35 -0400 |
commit | 14bc174ad3d23b43121a4696bc30c3235d4975ec (patch) | |
tree | e01c20d00012541432feef7399a21a278ed64eb2 /gdb/testsuite/gdb.python/py-objfile-script.c | |
parent | 02d04eac24f497e34ac9869bac5bfb1e044a6b62 (diff) | |
download | binutils-14bc174ad3d23b43121a4696bc30c3235d4975ec.zip binutils-14bc174ad3d23b43121a4696bc30c3235d4975ec.tar.gz binutils-14bc174ad3d23b43121a4696bc30c3235d4975ec.tar.bz2 |
gdb/testsuite: fix breakpoint script output in gdb.mi/mi-break.exp
Commit 9db0d8536dbc ("gdb/mi: fix breakpoint script field output") fixed
the output of the script key in the MI breakpoint output, from
script={"print 10","continue"}
to
script=["print 10","continue"]
However, it missed updating this test case, which still tests for the
old (broken) form, causing:
FAIL: gdb.mi/mi-break.exp: mi-mode=main: test_breakpoint_commands: breakpoint commands: check that commands are set (unexpected output)
FAIL: gdb.mi/mi-break.exp: mi-mode=separate: test_breakpoint_commands: breakpoint commands: check that commands are set (unexpected output)
Update the test to expect the new form.
Change-Id: I174919d4eea53e96d914ca9bd1cf6f01c8de30b8
Diffstat (limited to 'gdb/testsuite/gdb.python/py-objfile-script.c')
0 files changed, 0 insertions, 0 deletions