This is the mail archive of the
gdb-patches@sourceware.org
mailing list for the GDB project.
Re: [PATCH] Add mi-threads-interrupt.exp test (PR 20039)
- From: Pedro Alves <palves at redhat dot com>
- To: Simon Marchi <simon dot marchi at ericsson dot com>, gdb-patches at sourceware dot org
- Date: Wed, 4 May 2016 10:20:06 +0100
- Subject: Re: [PATCH] Add mi-threads-interrupt.exp test (PR 20039)
- Authentication-results: sourceware.org; auth=none
- References: <1462305612-16493-1-git-send-email-simon dot marchi at ericsson dot com> <5983d4d2-016a-8020-c109-cb7ea2cfd179 at redhat dot 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.
Woke up this morning realizing that I hadn't done this for so long
myself that I had forgotten how I used to do it. We don't really
need a board file -- as described in the TestingGDB wiki page [1],
we can use GDBFLAGS from the command line for this:
$ make check RUNTESTFLAGS="GDBFLAGS='-ex set\ mi-async\ on'" TESTS="gdb.mi/mi-threads-interrupt.exp"
...
FAIL: gdb.mi/mi-threads-interrupt.exp: interrupt #1 (unknown output after running)
FAIL: gdb.mi/mi-threads-interrupt.exp: continue #2
[1] https://sourceware.org/gdb/wiki/TestingGDB
Thanks,
Pedro Alves