From: Jan Kratochvil <jan.kratochvil@redhat.com>
To: Tom de Vries <tdevries@suse.de>
Cc: "gdb-patches@sourceware.org" <gdb-patches@sourceware.org>,
Alan Hayward <alan.hayward@arm.com>
Subject: Re: [RFC][gdb/testsuite] Remove breakpoint command in gdb.base/ui-redirect.exp
Date: Wed, 04 Sep 2019 11:49:00 -0000 [thread overview]
Message-ID: <20190904114855.GA13625@host1.jankratochvil.net> (raw)
In-Reply-To: <3150ecd9-9221-4360-6a16-563b3c5ef1ab@suse.de>
On Tue, 03 Sep 2019 19:43:44 +0200, Tom de Vries wrote:
> I noticed a bit in gdb.base/ui-redirect.exp that sets a breakpoint
> command on main, but then due to runto_main, the break point is deleted:
...
> In the original commit ( submission here
> https://sourceware.org/ml/gdb-patches/2010-09/msg00120.html ) there was
> no runto_main, and the breakpoint command was not triggered either.
>
> Is this some artefact, and can it be removed, or is it actually testing
> something related to redirection?
It looks to me the patch which added the "runto_main" part:
commit ca1285d17534cff3041c07ac7841288e1b3ba19c
Author: Alan Hayward <alan.hayward@arm.com>
Date: Fri May 17 14:15:01 2019 +0100
Add debug redirect option
disabled the regression testing.
"runto_main" should be removed otherwise the testcase does not test anything
(or it just tests less).
Jan
next prev parent reply other threads:[~2019-09-04 11:49 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-09-03 17:43 Tom de Vries
2019-09-04 10:59 ` Andrew Burgess
2019-09-04 11:57 ` Jan Kratochvil
2019-09-04 11:49 ` Jan Kratochvil [this message]
2019-09-05 7:35 ` [PATCH][gdb/testsuite] Restore breakpoint command in ui-redirect.exp Tom de Vries
2019-09-05 12:03 ` Jan Kratochvil
2019-09-05 12:07 ` Tom de Vries
2019-09-05 12:20 ` Pedro Alves
2019-09-05 12:42 ` Tom de Vries
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=20190904114855.GA13625@host1.jankratochvil.net \
--to=jan.kratochvil@redhat.com \
--cc=alan.hayward@arm.com \
--cc=gdb-patches@sourceware.org \
--cc=tdevries@suse.de \
/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