From: Pedro Alves <palves@redhat.com>
To: Don Breazeal <donb@codesourcery.com>, gdb-patches@sourceware.org
Subject: Re: [PATCH v2 1/3] Target remote mode fork and exec tests
Date: Tue, 08 Dec 2015 12:58:00 -0000 [thread overview]
Message-ID: <5666D3E5.1060506@redhat.com> (raw)
In-Reply-To: <1449526447-10039-2-git-send-email-donb@codesourcery.com>
On 12/07/2015 10:14 PM, Don Breazeal wrote:
> +# In remote mode we cannot use the 'set args' command, and this
> +# test requires it.
> +if { [target_info exists gdb_protocol] } then {
> + if { [target_info gdb_protocol] == "remote" } then {
> + continue
> + }
> }
>
It looks a little odd to me not to merge that into a single if:
if { [target_info exists gdb_protocol]
&& [target_info gdb_protocol] == "remote" } {
continue
}
> if {[gdb_compile_pthreads "${srcdir}/${subdir}/${srcfile}" "${binfile}" executable {debug}] != "" } {
> diff --git a/gdb/testsuite/gdb.threads/fork-plus-threads.exp b/gdb/testsuite/gdb.threads/fork-plus-threads.exp
> index 2b34b6c..d5a915b 100644
> --- a/gdb/testsuite/gdb.threads/fork-plus-threads.exp
> +++ b/gdb/testsuite/gdb.threads/fork-plus-threads.exp
> @@ -20,6 +20,14 @@
> #
> # See https://sourceware.org/bugzilla/show_bug.cgi?id=18600
>
> +# In remote mode, we cannot continue debugging after all
> +# inferiors have terminated, and this test requires that.
> +if { [target_info exists gdb_protocol] } then {
> + if { [target_info gdb_protocol] == "remote" } then {
> + continue
> + }
> +}
Likewise.
In any case, this is OK.
Thanks,
Pedro Alves
next prev parent reply other threads:[~2015-12-08 12:58 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-11-06 23:56 [PATCH 0/3] Target remote mode fork and exec support Don Breazeal
2015-11-06 23:57 ` [PATCH 1/3] Target remote mode fork and exec events Don Breazeal
2015-11-20 13:04 ` Pedro Alves
2015-11-20 16:50 ` Don Breazeal
2015-12-07 22:14 ` [PATCH v2 0/3] Target remote mode fork and exec support Don Breazeal
2015-12-07 22:14 ` [PATCH v2 1/3] Target remote mode fork and exec tests Don Breazeal
2015-12-08 12:58 ` Pedro Alves [this message]
2015-12-14 19:29 ` [pushed] " Don Breazeal
2015-12-07 22:14 ` [PATCH v2 2/3] Target remote mode fork and exec events Don Breazeal
2015-12-08 12:55 ` Pedro Alves
2015-12-14 19:29 ` Don Breazeal
2015-12-15 10:52 ` Pedro Alves
2015-12-07 22:15 ` [PATCH v2 3/3] Target remote mode fork and exec docs Don Breazeal
2015-12-08 13:07 ` Pedro Alves
2015-12-14 19:30 ` [pushed] " Don Breazeal
2015-12-08 13:11 ` [PATCH v2 0/3] Target remote mode fork and exec support Pedro Alves
2015-11-06 23:57 ` [PATCH 2/3] Target remote mode fork and exec tests Don Breazeal
2015-11-06 23:57 ` [PATCH 3/3] Target remote mode fork and exec docs Don Breazeal
2015-11-07 8:18 ` Eli Zaretskii
2015-11-12 1:00 ` Don Breazeal
2015-11-12 1:00 ` Don Breazeal
2015-11-12 16:48 ` Eli Zaretskii
2015-11-13 1:13 ` Don Breazeal
2015-11-13 8:16 ` Eli Zaretskii
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=5666D3E5.1060506@redhat.com \
--to=palves@redhat.com \
--cc=donb@codesourcery.com \
--cc=gdb-patches@sourceware.org \
/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