From 2c415c0f382fd6361d9d702ebdd71cd6d6a06d19 Mon Sep 17 00:00:00 2001 From: Yao Qi Date: Fri, 15 Mar 2013 01:33:40 +0000 Subject: [PATCH] gdb/testsuite/ * gdb.base/condbreak.exp: Add semicolon back which was removed by my previous commit. --- gdb/testsuite/ChangeLog | 5 +++++ gdb/testsuite/gdb.base/condbreak.exp | 2 +- 2 files changed, 6 insertions(+), 1 deletion(-) diff --git a/gdb/testsuite/ChangeLog b/gdb/testsuite/ChangeLog index b0139d0e9d0..2b86ab0c640 100644 --- a/gdb/testsuite/ChangeLog +++ b/gdb/testsuite/ChangeLog @@ -1,3 +1,8 @@ +2013-03-15 Yao Qi + + * gdb.base/condbreak.exp: Add semicolon back which was removed + by my previous commit. + 2013-03-14 Yao Qi * config/monitor.exp (gdb_target_cmd): Remove semicolon after diff --git a/gdb/testsuite/gdb.base/condbreak.exp b/gdb/testsuite/gdb.base/condbreak.exp index 1f28c256b4d..c09228cd529 100644 --- a/gdb/testsuite/gdb.base/condbreak.exp +++ b/gdb/testsuite/gdb.base/condbreak.exp @@ -165,7 +165,7 @@ gdb_test "continue" "Continuing\\..*Breakpoint \[0-9\]+, main \\(argc=.*, argv=. # stop location, but avoids clutter when possible. # # Suppose you have a function written completely on one source line, like: -# int foo (int x) { return 0 } +# int foo (int x) { return 0; } # Setting a breakpoint at `foo' actually places the breakpoint after # foo's prologue. # -- 2.30.2