From: Jan Kratochvil <jan.kratochvil@redhat.com>
To: Joel Brobecker <brobecker@adacore.com>
Cc: Stan Shebs <stanshebs@earthlink.net>,
Yao Qi <yao@codesourcery.com>,
gdb-patches@sourceware.org
Subject: [commit#2] testsuite: gdb.base/dprintf.exp PR 12649 race [Re: [PATCH v2] dynamic printf]
Date: Tue, 15 May 2012 13:37:00 -0000 [thread overview]
Message-ID: <20120515133644.GA18167@host2.jankratochvil.net> (raw)
In-Reply-To: <20120515133340.GQ10253@adacore.com>
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
}
next prev parent reply other threads:[~2012-05-15 13:37 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-05-08 6:27 [PATCH v2] dynamic printf Stan Shebs
2012-05-08 7:50 ` Yao Qi
2012-05-14 15:54 ` Stan Shebs
2012-05-15 4:10 ` [commit] Fix spu-tdep.c build regression [Re: [PATCH v2] dynamic printf] Jan Kratochvil
2012-05-15 10:24 ` Jim Meyering
2012-05-15 13:10 ` [commit] testsuite: gdb.base/dprintf.exp PR 12649 race " Jan Kratochvil
2012-05-15 13:34 ` Joel Brobecker
2012-05-15 13:37 ` Jan Kratochvil [this message]
2012-05-16 20:17 ` [PATCH v2] dynamic printf Tom Tromey
2012-05-16 20:46 ` Stan Shebs
2012-05-16 20:52 ` Pedro Alves
2012-05-16 22:25 ` Stan Shebs
2012-05-17 1:56 ` Tom Tromey
2012-05-18 15:38 ` Pedro Alves
2012-05-16 20:53 ` Pedro Alves
2012-05-16 21:06 ` Tom Tromey
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20120515133644.GA18167@host2.jankratochvil.net \
--to=jan.kratochvil@redhat.com \
--cc=brobecker@adacore.com \
--cc=gdb-patches@sourceware.org \
--cc=stanshebs@earthlink.net \
--cc=yao@codesourcery.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox