From: Joel Brobecker <brobecker@adacore.com>
To: Jan Kratochvil <jan.kratochvil@redhat.com>
Cc: Stan Shebs <stanshebs@earthlink.net>,
Yao Qi <yao@codesourcery.com>,
gdb-patches@sourceware.org
Subject: Re: [commit] testsuite: gdb.base/dprintf.exp PR 12649 race [Re: [PATCH v2] dynamic printf]
Date: Tue, 15 May 2012 13:34:00 -0000 [thread overview]
Message-ID: <20120515133340.GQ10253@adacore.com> (raw)
In-Reply-To: <20120515130954.GA16932@host2.jankratochvil.net>
> --- src/gdb/testsuite/gdb.base/dprintf.exp 2012/05/14 15:38:41 1.1
> +++ src/gdb/testsuite/gdb.base/dprintf.exp 2012/05/15 13:08:58 1.2
> @@ -24,7 +24,9 @@
> set dp_location1 [gdb_get_line_number "set dprintf 1 here"]
>
> gdb_breakpoint "main"
> -gdb_run_cmd
> +if ![runto main] {
> + return -1
> +}
I think you can also remove the breakpoint on "main", since
"runto" deletes all breakpoints and inserts a new one.
--
Joel
next prev parent reply other threads:[~2012-05-15 13:34 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 [this message]
2012-05-15 13:37 ` [commit#2] " Jan Kratochvil
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=20120515133340.GQ10253@adacore.com \
--to=brobecker@adacore.com \
--cc=gdb-patches@sourceware.org \
--cc=jan.kratochvil@redhat.com \
--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