From: Pedro Alves <palves@redhat.com>
To: Simon Marchi <simon.marchi@ericsson.com>, gdb-patches@sourceware.org
Subject: Re: [PATCH] Add mi-threads-interrupt.exp test (PR 20039)
Date: Tue, 03 May 2016 21:59:00 -0000 [thread overview]
Message-ID: <35886665-b98f-84c9-8683-f59d53f98b95@redhat.com> (raw)
In-Reply-To: <5983d4d2-016a-8020-c109-cb7ea2cfd179@redhat.com>
On 05/03/2016 10:57 PM, Pedro Alves wrote:
> AFAICS, the test relies on "set mi-async off". Could you make sure that
> if you run it against a board file that forces that on, the test either
> passes (probably with -exec-interrupt in async mode) or is skipped?
> See mi_detect_async and the async global.
Alternatively, force set mi-async off in the test.
Thanks,
Pedro Alves
next prev parent reply other threads:[~2016-05-03 21:59 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-05-03 20:00 Simon Marchi
2016-05-03 21:57 ` Pedro Alves
2016-05-03 21:59 ` Pedro Alves [this message]
2016-05-03 22:04 ` Pedro Alves
2016-05-04 9:20 ` Pedro Alves
2016-05-04 18:04 ` Simon Marchi
2016-05-04 19:27 ` Pedro Alves
2016-05-04 14:34 ` Simon Marchi
2016-05-04 15:07 ` Pedro Alves
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=35886665-b98f-84c9-8683-f59d53f98b95@redhat.com \
--to=palves@redhat.com \
--cc=gdb-patches@sourceware.org \
--cc=simon.marchi@ericsson.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).