This is the mail archive of the
gdb-patches@sourceware.org
mailing list for the GDB project.
Re: [patch] Check threads after using agent
- From: Pedro Alves <palves at redhat dot com>
- To: Yao Qi <yao at codesourcery dot com>
- Cc: gdb-patches at sourceware dot org
- Date: Fri, 17 Feb 2012 10:09:30 +0000
- Subject: Re: [patch] Check threads after using agent
- References: <4F3E0409.3010804@codesourcery.com>
On 02/17/2012 07:38 AM, Yao Qi wrote:
> In Pedro's explanation on why we should stop "debugging thread" before
> access inferior via ptrace [1], `info threads' is used to expose the
> problem and answer the question. I think it is worth adding it into
> test suite.
>
> If we don't stop "debugging thread" when running inferior command, in
> this test, we will get a fail.
>
> info threads 3 2 1^M
> [New Thread 32316]^M
> [New Thread 32317]^M
> Id Target Id Frame ^M
> 3 Thread 32317 Remote failure reply: E01^M
> (gdb) FAIL: gdb.trace/strace.exp: info_marker info threads
>
> This test is to about checking thread 1,2,3 can be listed without error.
> OK to apply?
Okay, thanks.
--
Pedro Alves