This is the mail archive of the
gdb-patches@sourceware.org
mailing list for the GDB project.
Re: [PATCH] gdbserver: Set flag `suspended' properly for new lwp.
- From: Pedro Alves <palves at redhat dot com>
- To: Yao Qi <yao at codesourcery dot com>
- Cc: gdb-patches at sourceware dot org
- Date: Thu, 10 May 2012 16:57:02 +0100
- Subject: Re: [PATCH] gdbserver: Set flag `suspended' properly for new lwp.
- References: <1336386285-22330-1-git-send-email-yao@codesourcery.com>
On 05/07/2012 11:24 AM, Yao Qi wrote:
> Occasionally I see the following fails when run it with `target-async on'
> and native-gdbserver.exp board file:
>
> Running ../../../gdb/gdb/testsuite/gdb.mi/mi-nsmoribund.exp ...
> FAIL: gdb.mi/mi-nsmoribund.exp: stop 0 (timeout)
> FAIL: gdb.mi/mi-nsmoribund.exp: stop 1 (timeout)
> FAIL: gdb.mi/mi-nsmoribund.exp: stop 2 (timeout)
> FAIL: gdb.mi/mi-nsmoribund.exp: stop 3 (timeout)
> FAIL: gdb.mi/mi-nsmoribund.exp: stop 4 (timeout)
> FAIL: gdb.mi/mi-nsmoribund.exp: stop 5 (timeout)
> FAIL: gdb.mi/mi-nsmoribund.exp: stop 6 (timeout)
> FAIL: gdb.mi/mi-nsmoribund.exp: stop 7 (timeout)
> FAIL: gdb.mi/mi-nsmoribund.exp: stop 8 (timeout)
> FAIL: gdb.mi/mi-nsmoribund.exp: stop 9 (timeout)
Interesting. I had never seen it, but an infinite loop running the test with:
$ (set -e; while true; do make check RUNTESTFLAGS="--target_board=native-gdbserver mi-nsmoribund.exp"; done)
indeed catches it after a while. /me looking at the patch/issue.
--
Pedro Alves