From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from simark.ca by simark.ca with LMTP id hflSAQPw6WASOwAAWB0awg (envelope-from ) for ; Sat, 10 Jul 2021 15:07:47 -0400 Received: by simark.ca (Postfix, from userid 112) id E9EBE1ED02; Sat, 10 Jul 2021 15:07:46 -0400 (EDT) X-Spam-Checker-Version: SpamAssassin 3.4.2 (2018-09-13) on simark.ca X-Spam-Level: X-Spam-Status: No, score=-1.0 required=5.0 tests=MAILING_LIST_MULTI autolearn=ham autolearn_force=no version=3.4.2 Received: from sourceware.org (server2.sourceware.org [8.43.85.97]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (2048 bits) server-digest SHA256) (No client certificate requested) by simark.ca (Postfix) with ESMTPS id D89661E79C for ; Sat, 10 Jul 2021 15:07:45 -0400 (EDT) Received: from server2.sourceware.org (localhost [IPv6:::1]) by sourceware.org (Postfix) with ESMTP id DB544384803C for ; Sat, 10 Jul 2021 19:07:43 +0000 (GMT) Received: from mail-wm1-f43.google.com (mail-wm1-f43.google.com [209.85.128.43]) by sourceware.org (Postfix) with ESMTPS id 893AC385C40F for ; Sat, 10 Jul 2021 19:07:31 +0000 (GMT) DMARC-Filter: OpenDMARC Filter v1.4.1 sourceware.org 893AC385C40F Authentication-Results: sourceware.org; dmarc=none (p=none dis=none) header.from=palves.net Authentication-Results: sourceware.org; spf=pass smtp.mailfrom=gmail.com Received: by mail-wm1-f43.google.com with SMTP id l17-20020a05600c1d11b029021f84fcaf75so1423256wms.1 for ; Sat, 10 Jul 2021 12:07:31 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:subject:from:to:references:message-id:date :user-agent:mime-version:in-reply-to:content-language :content-transfer-encoding; bh=opdssRioZcadDt9Oi7bDRh26A2mEZQ7E2eVLRCEic2Q=; b=Wwu0TM248TVb5njmkeWgZHYHzIKW4MphnxtCW7Dj1Tlufy8xLgkKdDZ/e9xz0+YUsu g+kfdm7uBEUKYLQ+gdA76omDxorsGEP/HjQXbj2rswP6P/JLOZJy6oaCXZeLRBMYRf5U KE50bpWdgjNgjvXGi05CagA9hImQ4yjlecASvBvd8atJhlcgOx8k6MxikwSMs62CK9cR YmL7uUkszPkOPGCvoKA445N9lGdb2/oAlOwT6Eq0eCEKGKDxJM/cKmpIDtkeiNyg7OHt HjaREC9H96N9qy9vBCaoiKVuUd52ahFYwM7Iiy9cGkkNNPbJJHen+IKsGVjW/lk4pzSc UYfA== X-Gm-Message-State: AOAM530JEU+Kt/SuVPEVl0cKezf3BrOc9a4A14PfOqyzdTJAMANKo5wo lbcgf7I7X5V9DcG2nXvVdL0JhWzEURCNng== X-Google-Smtp-Source: ABdhPJyW6MQpwAJrljcT9h40gAyxrZm8ZF5AcWlpcHqY/LGbU2h1ig8LvaYspYsoUngl7SSerSxW+w== X-Received: by 2002:a1c:4e0b:: with SMTP id g11mr5604298wmh.167.1625944050099; Sat, 10 Jul 2021 12:07:30 -0700 (PDT) Received: from ?IPv6:2001:8a0:f932:6a00:6b6e:c7b6:c5a7:aac3? ([2001:8a0:f932:6a00:6b6e:c7b6:c5a7:aac3]) by smtp.gmail.com with ESMTPSA id y13sm9058001wrp.80.2021.07.10.12.07.28 (version=TLS1_3 cipher=TLS_AES_128_GCM_SHA256 bits=128/128); Sat, 10 Jul 2021 12:07:29 -0700 (PDT) Subject: Re: [PATCH 2/2] glibc-2.34: Fix internal error when running gdb.base/gdb-sigterm.exp From: Pedro Alves To: Kevin Buettner , gdb-patches@sourceware.org References: <20210710025129.201884-1-kevinb@redhat.com> <20210710025129.201884-3-kevinb@redhat.com> Message-ID: Date: Sat, 10 Jul 2021 20:07:28 +0100 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:78.0) Gecko/20100101 Thunderbird/78.11.0 MIME-Version: 1.0 In-Reply-To: <20210710025129.201884-3-kevinb@redhat.com> Content-Type: text/plain; charset=utf-8 Content-Language: en-US Content-Transfer-Encoding: 7bit X-BeenThere: gdb-patches@sourceware.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: Gdb-patches mailing list List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: gdb-patches-bounces+public-inbox=simark.ca@sourceware.org Sender: "Gdb-patches" Hi Kevin! On 2021-07-10 3:51 a.m., Kevin Buettner via Gdb-patches wrote: > The reason that the problem occurs with glibc-2.34 is that > libthread_db will always be loaded now; thus the wait() machinery > found in linux-thread-db.c is used instead of linux_nat_target::wait > (which is found in linux-nat.c). > > gdb/ChangeLog: > > * thread.c (any_thread_of_inferior): Don't call inferior_thread() > when there is no current thread. This isn't right. The real bug is that inferior_ptid and current_thread_ got out of sync. Where did that happen? What set inferior_ptid without using switch_to_thread & friends?