From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 21331 invoked by alias); 20 Feb 2012 12:32:55 -0000 Received: (qmail 21319 invoked by uid 22791); 20 Feb 2012 12:32:54 -0000 X-SWARE-Spam-Status: No, hits=-6.6 required=5.0 tests=AWL,BAYES_00,RCVD_IN_DNSWL_HI,SPF_HELO_PASS,T_RP_MATCHES_RCVD X-Spam-Check-By: sourceware.org Received: from mx1.redhat.com (HELO mx1.redhat.com) (209.132.183.28) by sourceware.org (qpsmtpd/0.43rc1) with ESMTP; Mon, 20 Feb 2012 12:32:39 +0000 Received: from int-mx11.intmail.prod.int.phx2.redhat.com (int-mx11.intmail.prod.int.phx2.redhat.com [10.5.11.24]) by mx1.redhat.com (8.14.4/8.14.4) with ESMTP id q1KCWdZw029908 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK) for ; Mon, 20 Feb 2012 07:32:39 -0500 Received: from host2.jankratochvil.net (ovpn-116-21.ams2.redhat.com [10.36.116.21]) by int-mx11.intmail.prod.int.phx2.redhat.com (8.14.4/8.14.4) with ESMTP id q1KCWZI4024307 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES128-SHA bits=128 verify=NO); Mon, 20 Feb 2012 07:32:37 -0500 Date: Mon, 20 Feb 2012 12:34:00 -0000 From: Jan Kratochvil To: Pedro Alves Cc: gdb-patches@sourceware.org Subject: Re: [PATCH 2/2] gdb.threads/attach-into-signal.exp: don't rely on linux native target's internal debug output Message-ID: <20120220123234.GA15276@host2.jankratochvil.net> References: <20120217193546.10029.74207.stgit@hit-nxdomain.opendns.com> <20120217193750.10029.58857.stgit@hit-nxdomain.opendns.com> <20120220085704.GA4966@host2.jankratochvil.net> <4F423BBC.10007@redhat.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <4F423BBC.10007@redhat.com> User-Agent: Mutt/1.5.21 (2010-09-15) X-IsSubscribed: yes Mailing-List: contact gdb-patches-help@sourceware.org; run by ezmlm Precedence: bulk List-Id: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: gdb-patches-owner@sourceware.org X-SW-Source: 2012-02/txt/msg00401.txt.bz2 On Mon, 20 Feb 2012 13:25:32 +0100, Pedro Alves wrote: > On 02/20/2012 08:57 AM, Jan Kratochvil wrote: > > On Fri, 17 Feb 2012 20:37:50 +0100, Pedro Alves wrote: > >> > + set test2 "pull thread list" > >> > + gdb_test_multiple "info threads" $test2 { > >> > + -re "\r\n$gdb_prompt $" { > >> > + } > >> > + } > > This can be just: > > gdb_test "info threads" ".*" "pull thread list" > > I avoided that on purpose, because that'd generate a PASS for every > attempt/iteration at trying to catch the signal. OK, I agree now. > > Still this is a bug of extended gdbserver mode. > > Yeah, it could be considered a bug. Not only of extended gdbserver > tough. It happens with all remote targets, and we have similar things > in other tests. One thing at a time though, otherwise, I'll never be > done. :-) Yes; but it should be somehow marked/filed, unless you track this issue already. Thanks, Jan