From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 23273 invoked by alias); 7 Jun 2004 22:36:36 -0000 Mailing-List: contact gdb-patches-help@sources.redhat.com; run by ezmlm Precedence: bulk List-Subscribe: List-Archive: List-Post: List-Help: , Sender: gdb-patches-owner@sources.redhat.com Received: (qmail 23264 invoked from network); 7 Jun 2004 22:36:35 -0000 Received: from unknown (HELO mx1.redhat.com) (66.187.233.31) by sourceware.org with SMTP; 7 Jun 2004 22:36:35 -0000 Received: from int-mx1.corp.redhat.com (int-mx1.corp.redhat.com [172.16.52.254]) by mx1.redhat.com (8.12.10/8.12.10) with ESMTP id i57MaZi5003833 for ; Mon, 7 Jun 2004 18:36:35 -0400 Received: from pobox.toronto.redhat.com (pobox.toronto.redhat.com [172.16.14.4]) by int-mx1.corp.redhat.com (8.11.6/8.11.6) with ESMTP id i57MaY019443; Mon, 7 Jun 2004 18:36:34 -0400 Received: from touchme.toronto.redhat.com (IDENT:postfix@touchme.toronto.redhat.com [172.16.14.9]) by pobox.toronto.redhat.com (8.12.8/8.12.8) with ESMTP id i57MaYtn007559; Mon, 7 Jun 2004 18:36:34 -0400 Received: from redhat.com (toocool.toronto.redhat.com [172.16.14.72]) by touchme.toronto.redhat.com (Postfix) with ESMTP id 253B480019B; Mon, 7 Jun 2004 18:36:34 -0400 (EDT) Message-ID: <40C4EDF2.7010909@redhat.com> Date: Mon, 07 Jun 2004 22:36:00 -0000 From: Jeff Johnston User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.4) Gecko/20030624 Netscape/7.1 MIME-Version: 1.0 To: Daniel Jacobowitz Cc: gdb-patches@sources.redhat.com, msnyder@redhat.com Subject: Re: [RFA]: Additional dead thread patch References: <40C4E3EB.1020807@redhat.com> <20040607215837.GA11052@nevyn.them.org> In-Reply-To: <20040607215837.GA11052@nevyn.them.org> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit X-SW-Source: 2004-06/txt/msg00142.txt.bz2 Daniel Jacobowitz wrote: > On Mon, Jun 07, 2004 at 05:53:47PM -0400, Jeff Johnston wrote: > >>After updating to current sources today, I have noticed a regression in >>print-threads.exp which is due to some missing logic in my June 4th patch. >>The problem is a timing issue (it does not occur for my June 4th build). >>There is a gdb_assert in thread_from_lwp() which gets triggered because the >>th_valid flag has not been set for a zombie thread's thread_info struct. >> >>This patch fills in the zombie thread's thread_info private area since the >>information is indeed valid and available. >> >>Ok to commit? >> >>-- Jeff J. >> >>2004-06-07 Jeff Johnston >> >> * thread-db.c (thread_get_info_callback): Fill in the thread_info >> struct if one exists, even if we are dealing with a zombie thread. >> > > > Yes, this is OK. > Patch checked in. Thanks. -- Jeff J.