From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 8375 invoked by alias); 9 Nov 2009 18:25:58 -0000 Received: (qmail 8343 invoked by uid 22791); 9 Nov 2009 18:25:56 -0000 X-SWARE-Spam-Status: No, hits=-2.5 required=5.0 tests=AWL,BAYES_00 X-Spam-Check-By: sourceware.org Received: from NaN.false.org (HELO nan.false.org) (208.75.86.248) by sourceware.org (qpsmtpd/0.43rc1) with ESMTP; Mon, 09 Nov 2009 18:25:52 +0000 Received: from nan.false.org (localhost [127.0.0.1]) by nan.false.org (Postfix) with ESMTP id 00AEB10CE9; Mon, 9 Nov 2009 18:25:51 +0000 (GMT) Received: from caradoc.them.org (209.195.188.212.nauticom.net [209.195.188.212]) by nan.false.org (Postfix) with ESMTP id D0F541065D; Mon, 9 Nov 2009 18:25:50 +0000 (GMT) Received: from drow by caradoc.them.org with local (Exim 4.69) (envelope-from ) id 1N7Yw2-00086j-15; Mon, 09 Nov 2009 13:25:50 -0500 Date: Mon, 09 Nov 2009 18:25:00 -0000 From: Daniel Jacobowitz To: Daniel Gutson Cc: Michael Snyder , "gdb-patches@sourceware.org" Subject: Re: [PATCH] gcore registers storing fix Message-ID: <20091109182550.GA30593@caradoc.them.org> Mail-Followup-To: Daniel Gutson , Michael Snyder , "gdb-patches@sourceware.org" References: <4AF4A505.4010600@codesourcery.com> <4AF72404.1070808@vmware.com> <4AF82E4E.8000500@codesourcery.com> <20091109153110.GA12924@caradoc.them.org> <4AF85CC0.2030002@codesourcery.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <4AF85CC0.2030002@codesourcery.com> User-Agent: Mutt/1.5.20 (2009-06-14) 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: 2009-11/txt/msg00156.txt.bz2 On Mon, Nov 09, 2009 at 03:17:36PM -0300, Daniel Gutson wrote: > The problem shows up when "in ??" appears. I think that the current > thread will never be shown in that way unless the test does fail. > That being said, I think that I could add the regex for the "*" in > order to looking into the current thread only. How is that different from the two following tests in gcore-thread.exp? # One thread in the corefile should be in the "thread2" function. gdb_test "info threads" ".* thread2 .*" \ "a corefile thread is executing thread2" # The thread2 thread should be marked as the current thread. gdb_test "info threads" ".*${nl}\\* ${horiz} thread2 .*" \ "thread2 is current thread in corefile" -- Daniel Jacobowitz CodeSourcery