From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from simark.ca by simark.ca with LMTP id IZsgBTe+3WEqUAAAWB0awg (envelope-from ) for ; Tue, 11 Jan 2022 12:28:23 -0500 Received: by simark.ca (Postfix, from userid 112) id 04C651F34E; Tue, 11 Jan 2022 12:28:23 -0500 (EST) X-Spam-Checker-Version: SpamAssassin 3.4.2 (2018-09-13) on simark.ca X-Spam-Level: X-Spam-Status: No, score=-2.0 required=5.0 tests=BAYES_00,DKIM_SIGNED, DKIM_VALID,DKIM_VALID_AU,MAILING_LIST_MULTI,RDNS_DYNAMIC,URIBL_BLOCKED autolearn=ham autolearn_force=no version=3.4.2 Received: from sourceware.org (ip-8-43-85-97.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 7E3E61EAA4 for ; Tue, 11 Jan 2022 12:28:22 -0500 (EST) Received: from server2.sourceware.org (localhost [IPv6:::1]) by sourceware.org (Postfix) with ESMTP id BC0C3389AC74 for ; Tue, 11 Jan 2022 17:28:21 +0000 (GMT) DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org BC0C3389AC74 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=sourceware.org; s=default; t=1641922101; bh=s4+03VhjPpW04obHel7LtKfL66V6NOpXL4UBuFwTo2Y=; h=Date:To:Subject:References:In-Reply-To:List-Id:List-Unsubscribe: List-Archive:List-Post:List-Help:List-Subscribe:From:Reply-To:Cc: From; b=PELmUxk0Abaur2riGHQR1j0f1BE3PujLN/kqC9JUPczpRSrzYOridoajpEIfDM+FM 4y2C+je4iIGETkZKMwy/my+w84f8dK35fbzXxgDj1trXWgcCY6LQHZkTrq1d/2F2z0 oNs7nUAOMjTkTjJT9bN13eQqRtKVHB3mom3ZB/bQ= Received: from smtp.gentoo.org (woodpecker.gentoo.org [140.211.166.183]) by sourceware.org (Postfix) with ESMTP id 465043858D39 for ; Tue, 11 Jan 2022 17:28:02 +0000 (GMT) DMARC-Filter: OpenDMARC Filter v1.4.1 sourceware.org 465043858D39 Received: by smtp.gentoo.org (Postfix, from userid 559) id 4E381343084; Tue, 11 Jan 2022 17:28:01 +0000 (UTC) Date: Tue, 11 Jan 2022 12:27:59 -0500 To: "Aktemur, Tankut Baris" Subject: Re: [PATCH] sim: filter out SIGSTKSZ [PR sim/28302] Message-ID: Mail-Followup-To: "Aktemur, Tankut Baris" , Joel Brobecker , "gdb-patches@sourceware.org" References: <20211003160916.13080-1-vapier@gentoo.org> MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha256; protocol="application/pgp-signature"; boundary="082oe3ZEnjhDdCuJ" Content-Disposition: inline In-Reply-To: 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: , From: Mike Frysinger via Gdb-patches Reply-To: Mike Frysinger Cc: "gdb-patches@sourceware.org" , Joel Brobecker Errors-To: gdb-patches-bounces+public-inbox=simark.ca@sourceware.org Sender: "Gdb-patches" --082oe3ZEnjhDdCuJ Content-Type: text/plain; charset=utf-8 Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On 11 Jan 2022 15:14, Aktemur, Tankut Baris wrote: > On Sunday, October 3, 2021 6:09 PM, Mike Frysinger wrote: > > We map target signals to host signals so we can propagate signals > > between the host & simulated worlds. That means we need to know > > the symbolic names & values of all signals that might be sent. > >=20 > > The tools that generate that list use signal.h and include all > > symbols that start with "SIG" so as to automatically include any > > new symbols that the C library might add. Unfortunately, this > > also picks up "SIGSTKSZ" which is not actually a signal itself, > > but a signal related setting -- it's the size of the stack when > > a signal is handled. > >=20 > > By itself this doesn't super matter as we will never see a signal > > with that same value (since the range of valid signals tend to be > > way less than 1024, and the size of the default signal stack will > > never be that small). But with recent glibc changes that make this > > into a dynamic value instead of a compile-time constant, some users > > see build failures when building the sim. > >=20 > > As suggested by Adam Sampson, update our scripts to ignore this > > symbol to simplify everything and avoid the build failure. > >=20 > > Bug: https://sourceware.org/PR28302 >=20 > This patch fixes a build problem that may be seen with GDB 11. Should > it be cherry-picked to gdb-11-branch to be included for the upcoming > 11.2 release? i don't normally pay much attention to branches. but i can cherry pick it back if people want it & branch maintainer approves it. -mike --082oe3ZEnjhDdCuJ Content-Type: application/pgp-signature; name="signature.asc" -----BEGIN PGP SIGNATURE----- iQIzBAABCAAdFiEEuQK1JxMl+JKsJRrUQWM7n+g39YEFAmHdvh4ACgkQQWM7n+g3 9YFYIA//Ybbdoxt7kluvojgEsDpHARX4u+fQ/wcIZ+74TwrvKtWEJAvtwzDf/Zti F1xZvrO7qUoi0cuem59Tu2P+KAEN3rkTl4O/83rriR6Hr6g2t4JhEy8MfwECu54m qdo70C58hnzZBewUlEaKN5vgmQY1EqOskE/9cUDlF5MsWOGSWi+8FEzP27GEOGGG ForTIczROojXKLR6gOAGojs7AHfjO3KWlCagwolGqmN/0XNkH/0Y5x/OeQFT3THn uNTHHwZ7ZYO1DqcBvrOmMfKHdttjUi0SyhQ84V+le7tDw/pg6NSYSE1Z8zCqbsI/ bP2EfTQcLYqyx0JI52pUuqfeCRR89NPA68+c/PyYIR/d6EvhPt6wesvWEbNEPqzs kg8Z1LGicqxXAWHEoV7pXjt5oQ+v4ABe68A81gMYkONSjBuVzUxzRRSKidELsteV eB/9sQ5go7cj6GVUynHA590T8pu09mCWhndJsVZvLMeNY12Hu1xK2Kw19QyWISJi QLLm5n5AtF/geY7fPpL7kgCfKSaD/vgxiGrYSVBMH8PIoaQrk4XERCXjyAOTsUn5 4JPgBjB3n+UcBUcpe/qf56bu5pkwJk5fFi/qQp26NhSrE7u3aBShL4DyciBg+yfJ rA/ek1sz1FrhuUT6R4ylieDVl+ilHeaBYB2fSRnrZlGFN28HQ7M= =veEh -----END PGP SIGNATURE----- --082oe3ZEnjhDdCuJ--