From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from simark.ca by simark.ca with LMTP id i1z0OLPn9V/5bQAAWB0awg (envelope-from ) for ; Wed, 06 Jan 2021 11:39:15 -0500 Received: by simark.ca (Postfix, from userid 112) id D186C1E940; Wed, 6 Jan 2021 11:39:15 -0500 (EST) X-Spam-Checker-Version: SpamAssassin 3.4.2 (2018-09-13) on simark.ca X-Spam-Level: X-Spam-Status: No, score=-1.1 required=5.0 tests=DKIM_SIGNED,DKIM_VALID, DKIM_VALID_AU,MAILING_LIST_MULTI,URIBL_BLOCKED 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 1A1D91E590 for ; Wed, 6 Jan 2021 11:39:15 -0500 (EST) Received: from server2.sourceware.org (localhost [IPv6:::1]) by sourceware.org (Postfix) with ESMTP id 577933947427; Wed, 6 Jan 2021 16:39:14 +0000 (GMT) DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org 577933947427 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=sourceware.org; s=default; t=1609951154; bh=h26VgMap0qsGe3T3MDW24SUTDF6tThc5byPpAWnlb6E=; h=References:In-Reply-To:Date:Subject:To:List-Id:List-Unsubscribe: List-Archive:List-Post:List-Help:List-Subscribe:From:Reply-To: From; b=N1+zoifN8Ku0OezDVqCD+Jl9KwZoG71xHulvEK81s68DVKzl1cZneXxBkFsIJzG0L mjKxASLvCRHpUQnZbP5D6uXiDDprVaozKS8i0CU31HVrG/5PeetKZYaXUn56Fxdd0o hH6tXbPkTyDz3bJr1vPIM32kqI/woWIFlmtbPy9Q= Received: from mail-lf1-x12a.google.com (mail-lf1-x12a.google.com [IPv6:2a00:1450:4864:20::12a]) by sourceware.org (Postfix) with ESMTPS id 08CEA384B13B for ; Wed, 6 Jan 2021 16:39:12 +0000 (GMT) DMARC-Filter: OpenDMARC Filter v1.3.2 sourceware.org 08CEA384B13B Received: by mail-lf1-x12a.google.com with SMTP id a12so7915814lfl.6 for ; Wed, 06 Jan 2021 08:39:11 -0800 (PST) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to; bh=RkN6awn40QlISMvNi+RxPBupy3E/XfQEaPy+ConQR/Y=; b=OJZg0o874sn6e3WkiG5wd5h45LiAO2oDlyWBg+5i1ZBpVebeoxulgyY1yhmp4dD/NC QZWiw0eWdC/PIzeZFUCuRl3yGbqr4fID4k28WwPifp4PktasQ2YCdI0CaTHSFKqhaWYJ Mjdu9qrxF408gE+dqdU6iRwnZrMxlXLXFxAAFbUqprGJAhEfpjrxkF6F2K9axyz25zvu i5WKL2uebM0gxSi/AP0E6ZS2ws8cTYtVTpmhZOXiHzD2HFzXCE1qFxvJxetoq5nAOTGJ HBrt6Tkrgv1SYUUO3kHBfFR6mJYy0mmYE3bNPRoxwPZegOB/Y1tmyKpNOIyegvc89fpw CuFg== X-Gm-Message-State: AOAM532mXym8FS77YF6jmX+F6agOaIO2Tft9pJ5Lja21kto8/ScxuZdv u39nndPl4aX33z+UH/WZNIwXaBvWOkudTX6JisbmrmxyG4kD4w== X-Google-Smtp-Source: ABdhPJy8WcCHKjGw5HCOEKyHijVbc9fOTfkPtTanYIqu+I/Hg3xneOGSNLeaU8X1FLNOJpovNDHLs4JP/RLx9CUbjv0= X-Received: by 2002:a2e:9ad3:: with SMTP id p19mr2237867ljj.286.1609951150229; Wed, 06 Jan 2021 08:39:10 -0800 (PST) MIME-Version: 1.0 References: In-Reply-To: Date: Wed, 6 Jan 2021 08:38:59 -0800 Message-ID: Subject: Re: AMD64_LINUX_frame_size To: gdb@sourceware.org Content-Type: text/plain; charset="UTF-8" X-Content-Filtered-By: Mailman/MimeDel 2.1.29 X-BeenThere: gdb@sourceware.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: Gdb mailing list List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , From: Walt Drummond via Gdb Reply-To: Walt Drummond Errors-To: gdb-bounces@sourceware.org Sender: "Gdb" After looking at this further, I think I understand AMD64_LINUX_frame_size and why it differs from the size of the kernel's rt_sigframe (differences between glibc's and the kernels' definition of sigset_t), but I don't understand how GDB arrived at 512 for AMD_LINUX_xstate. The kernel's math frame, which also contains the extended state information, is 840 bytes. I feel I must be missing something. Any pointers? Thanks. On Mon, Jan 4, 2021 at 10:30 AM Walt Drummond wrote: > I'm trying to understand the relationship between the > AMD64_LINUX_frame_size constant and the kernel's signal stack layout. Is > there any documentation or commentary that describes how we got to the > current value? > > Thanks. > >