From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 33553 invoked by alias); 5 Apr 2017 21:15:48 -0000 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 Received: (qmail 33535 invoked by uid 89); 5 Apr 2017 21:15:47 -0000 Authentication-Results: sourceware.org; auth=none X-Virus-Found: No X-Spam-SWARE-Status: No, score=-6.4 required=5.0 tests=BAYES_00,FREEMAIL_FROM,GIT_PATCH_2,RCVD_IN_DNSWL_NONE,RCVD_IN_SORBS_SPAM,SPF_PASS autolearn=ham version=3.3.2 spammy=HERE X-HELO: mail-wr0-f196.google.com Received: from mail-wr0-f196.google.com (HELO mail-wr0-f196.google.com) (209.85.128.196) by sourceware.org (qpsmtpd/0.93/v0.84-503-g423c35a) with ESMTP; Wed, 05 Apr 2017 21:15:46 +0000 Received: by mail-wr0-f196.google.com with SMTP id g19so6094723wrb.0 for ; Wed, 05 Apr 2017 14:15:47 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:from:to:subject:date:message-id:in-reply-to :references; bh=+C8LdKkQ3ouJNBTpfffvRcqBsz78hYzSwNKimLLSPM0=; b=IBLfFRpkhWjFRABASGuLrNzf+f+JQMMYHALhwQBDAjoKkoB6Mcr8/vqun6La0PdqC0 bDL5v0ppRSxz13gD9K0ryZ2LdLbPaeUOJ8v+1y0pQAD0lEwZcGw/FyoP5YtcPD1bRCG1 jIBYVqlOVv8RuddbQEiMHfR/WBdbeAWzCpR0YfPAZ/j3brjHUfwQsY/CpI7IkKzG+Pqv vlw34Gq5NQW4jQumNSUiOSSXj83i1FZsJoUkvTFVMIQVanYwjUWTKRPQzGR+BC3wbOS3 TrlLeJCbRdDGRKRboAVyhAzEK5/+6V1GywUgBc0Fm4zePwmZu8YuLsP0HHfUT+xBq7WJ us3A== X-Gm-Message-State: AFeK/H28HnWQ+8xZpFYKANAN9GF7P49chHTLxB0G07cppgpF3dwPua8hU5yWT6QpSeXQSA== X-Received: by 10.28.128.209 with SMTP id b200mr21951693wmd.140.1491426945328; Wed, 05 Apr 2017 14:15:45 -0700 (PDT) Received: from E107787-LIN.Home ([194.214.185.158]) by smtp.gmail.com with ESMTPSA id o22sm12800012wro.45.2017.04.05.14.15.44 for (version=TLS1_2 cipher=ECDHE-RSA-AES128-SHA bits=128/128); Wed, 05 Apr 2017 14:15:44 -0700 (PDT) From: Yao Qi X-Google-Original-From: Yao Qi To: gdb-patches@sourceware.org Subject: [PATCH 0/2] Don't delete thread_info if refcount isn't zero Date: Wed, 05 Apr 2017 21:15:00 -0000 Message-Id: <1491426942-6306-1-git-send-email-yao.qi@linaro.org> In-Reply-To: <1f525e52-f547-63ac-0a31-e92686c9caf8@redhat.com> References: <1f525e52-f547-63ac-0a31-e92686c9caf8@redhat.com> X-IsSubscribed: yes X-SW-Source: 2017-04/txt/msg00129.txt.bz2 After Pedro explained the refcount in thread_info, previously I completely misunderstood it. Here is the updated patch set. Regression tested on x86_64-linux. *** BLURB HERE *** Yao Qi (2): Hoist code on marking thread as exited Don't delete thread_info if refcount isn't zero gdb/gdbthread.h | 33 ++++++++++++++--- gdb/infrun.c | 4 +-- gdb/thread.c | 107 +++++++++++++++++++++++--------------------------------- 3 files changed, 73 insertions(+), 71 deletions(-) -- 1.9.1