gdb/testsuite: fix breakpoint script output in gdb.mi/mi-break.exp
authorSimon Marchi <simon.marchi@polymtl.ca>
Tue, 16 Aug 2022 14:41:47 +0000 (10:41 -0400)
committerSimon Marchi <simon.marchi@polymtl.ca>
Tue, 16 Aug 2022 14:43:35 +0000 (10:43 -0400)
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

gdb/testsuite/gdb.mi/mi-break.exp

index b64fe196940498df71978ee3d11dbbca2f743cfe..24353379ffe76b73d3bc55585244d3cc16672de9 100644 (file)
@@ -203,7 +203,7 @@ proc_with_prefix test_breakpoint_commands {} {
     # seen.
     set bp_script [mi_make_breakpoint -number 7 -disp keep -func callee2 \
                       -file ".*basics.c" -line $line_callee2_body \
-                      -script {\{"print 10","continue"\}}]
+                      -script {\["print 10","continue"\]}]
     mi_gdb_test "-break-info 7" \
        "\\^done,[mi_make_breakpoint_table [list $bp_script]]" \
        "breakpoint commands: check that commands are set"