[commit#2] testsuite: gdb.base/dprintf.exp PR 12649 race [Re: [PATCH v2] dynamic printf]
Jan Kratochvil
jan.kratochvil@redhat.com
Tue May 15 13:37:00 GMT 2012
On Tue, 15 May 2012 15:33:40 +0200, Joel Brobecker wrote:
> I think you can also remove the breakpoint on "main", since
> "runto" deletes all breakpoints and inserts a new one.
yes:
http://sourceware.org/ml/gdb-cvs/2012-05/msg00108.html
--- src/gdb/testsuite/ChangeLog 2012/05/15 13:08:57 1.3190
+++ src/gdb/testsuite/ChangeLog 2012/05/15 13:36:17 1.3191
@@ -3,6 +3,8 @@
PR testsuite/12649
* gdb.base/dprintf.exp: Replace gdb_run_cmd by runto main.
+ * gdb.base/dprintf.exp: Remove now redundant breakpoint for main.
+
2012-05-14 Sergio Durigan Junior <sergiodj@redhat.com>
* gdb.base/stap-probe.exp (stap_test): Remove calls to
--- src/gdb/testsuite/gdb.base/dprintf.exp 2012/05/15 13:08:58 1.2
+++ src/gdb/testsuite/gdb.base/dprintf.exp 2012/05/15 13:36:18 1.3
@@ -23,7 +23,6 @@
set bp_location1 [gdb_get_line_number "set breakpoint 1 here"]
set dp_location1 [gdb_get_line_number "set dprintf 1 here"]
-gdb_breakpoint "main"
if ![runto main] {
return -1
}
More information about the Gdb-patches
mailing list