From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from simark.ca by simark.ca with LMTP id WzZqKjfx5meoyh0AWB0awg (envelope-from ) for ; Fri, 28 Mar 2025 14:57:59 -0400 Received: by simark.ca (Postfix, from userid 112) id A08731E0C3; Fri, 28 Mar 2025 14:57:59 -0400 (EDT) X-Spam-Checker-Version: SpamAssassin 4.0.1 (2024-03-25) on simark.ca X-Spam-Level: X-Spam-Status: No, score=-5.3 required=5.0 tests=ARC_SIGNED,ARC_VALID,BAYES_00, MAILING_LIST_MULTI,RCVD_IN_DNSWL_MED autolearn=ham autolearn_force=no version=4.0.1 Received: from server2.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 ECDSA (prime256v1) server-digest SHA256) (No client certificate requested) by simark.ca (Postfix) with ESMTPS id 74AFE1E0C0 for ; Fri, 28 Mar 2025 14:57:56 -0400 (EDT) Received: from server2.sourceware.org (localhost [IPv6:::1]) by sourceware.org (Postfix) with ESMTP id 22F613830611 for ; Fri, 28 Mar 2025 18:57:56 +0000 (GMT) DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org 22F613830611 Received: from smtp.gentoo.org (woodpecker.gentoo.org [140.211.166.183]) by sourceware.org (Postfix) with ESMTP id 284923857BA5 for ; Fri, 28 Mar 2025 18:57:26 +0000 (GMT) DMARC-Filter: OpenDMARC Filter v1.4.2 sourceware.org 284923857BA5 Authentication-Results: sourceware.org; dmarc=pass (p=none dis=none) header.from=gentoo.org Authentication-Results: sourceware.org; spf=pass smtp.mailfrom=gentoo.org ARC-Filter: OpenARC Filter v1.0.0 sourceware.org 284923857BA5 Authentication-Results: server2.sourceware.org; arc=none smtp.remote-ip=140.211.166.183 ARC-Seal: i=1; a=rsa-sha256; d=sourceware.org; s=key; t=1743188246; cv=none; b=O/BFYiMpC3PfH4tZ1Qg0LOORE0um2Kjj1fK9XO0Ww04vtkE0lEBtdckfl2wECoBTdiSz19zImdQCRmSPVXTNK6cGH8b/AnQwcy3D+o22QkH/p9Zi6r3Fi6QCjnUZy7SnjPTSEuTB8wAJq4UTjZbCWtDw0A/uxh2SoVHqqVvcqJc= ARC-Message-Signature: i=1; a=rsa-sha256; d=sourceware.org; s=key; t=1743188246; c=relaxed/simple; bh=eHaY0KI6gi0LgH+qA0rIh1StVpplMsnu+7nwNS31hhE=; h=From:To:Subject:Date:Message-ID:MIME-Version; b=wiM81J7swXkRN+64D9flwih5KH+gfJewQeYPKZe2DYe1iADXc5uMvGIyOSqfhq/WcY0/i8fxgbhRAHwHur77kZHmmO2aEWEIn8rnkVbxWXTrMoaBtADhq8Woym6EdQ4qoKgg1DHtED+FL597bT0EchUJDZr2RmUjhULCzrfPF88= ARC-Authentication-Results: i=1; server2.sourceware.org DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org 284923857BA5 Received: from mop.sam.mop (unknown [82.8.138.118]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange ECDHE (prime256v1) server-signature RSA-PSS (4096 bits) server-digest SHA256) (No client certificate requested) (Authenticated sender: sam) by smtp.gentoo.org (Postfix) with ESMTPSA id D59FC343137; Fri, 28 Mar 2025 18:57:23 +0000 (UTC) From: Sam James To: Keith Seitz Cc: Tom Tromey , gdb-patches@sourceware.org Subject: Re: [PATCH] Fix gstack issues In-Reply-To: <4dfbfd1e-5d58-4bad-96ce-49da430e8df2@redhat.com> Organization: Gentoo References: <85d8b0e904d7893d55db6531edb64d4a16062a46.1743090890.git.keiths@redhat.com> <87bjtmuypo.fsf@tromey.com> <764b45b5-f1ba-4e93-92dc-e1a0388aa0dd@redhat.com> <4dfbfd1e-5d58-4bad-96ce-49da430e8df2@redhat.com> User-Agent: mu4e 1.12.9; emacs 31.0.50 Date: Fri, 28 Mar 2025 18:57:21 +0000 Message-ID: <87jz893rvy.fsf@gentoo.org> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable X-BeenThere: gdb-patches@sourceware.org X-Mailman-Version: 2.1.30 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 Keith Seitz writes: > On 3/28/25 8:17 AM, Keith Seitz wrote: >> On 3/27/25 11:15 AM, Tom Tromey wrote: >>>>>>>> "Keith" =3D=3D Keith Seitz writes: >>> >>> Makes sense to me.=C2=A0 Thanks for doing this. >>> Approved-By: Tom Tromey >> Thanks, Tom. I've waited until this morning to push, fearing that >> various CIs would detect something, but I think there's been time >> for that, and I've pushed the patch. > > BTW, Gwen raises the question: Is this something we want to include > for 16.3? (If so, please backport my fixes as well -- thank you!) > > Keith