From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from simark.ca by simark.ca with LMTP id m4rBIE1BJmLiDwAAWB0awg (envelope-from ) for ; Mon, 07 Mar 2022 12:30:53 -0500 Received: by simark.ca (Postfix, from userid 112) id 7593C1F3CA; Mon, 7 Mar 2022 12:30:53 -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.7 required=5.0 tests=BAYES_00,DKIM_INVALID, DKIM_SIGNED,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 E38EB1EDF0 for ; Mon, 7 Mar 2022 12:30:52 -0500 (EST) Received: from server2.sourceware.org (localhost [IPv6:::1]) by sourceware.org (Postfix) with ESMTP id 4C9553857C7D for ; Mon, 7 Mar 2022 17:30:52 +0000 (GMT) Received: from gproxy3-pub.mail.unifiedlayer.com (gproxy3-pub.mail.unifiedlayer.com [69.89.30.42]) by sourceware.org (Postfix) with ESMTPS id 08416385841F for ; Mon, 7 Mar 2022 17:30:38 +0000 (GMT) DMARC-Filter: OpenDMARC Filter v1.4.1 sourceware.org 08416385841F Authentication-Results: sourceware.org; dmarc=none (p=none dis=none) header.from=tromey.com Authentication-Results: sourceware.org; spf=pass smtp.mailfrom=tromey.com Received: from cmgw12.mail.unifiedlayer.com (unknown [10.0.90.127]) by progateway5.mail.pro1.eigbox.com (Postfix) with ESMTP id 6618710047F46 for ; Mon, 7 Mar 2022 17:30:37 +0000 (UTC) Received: from box5379.bluehost.com ([162.241.216.53]) by cmsmtp with ESMTP id RHBsnMjP4ctgJRHBtnQ9mi; Mon, 07 Mar 2022 17:30:37 +0000 X-Authority-Reason: nr=8 X-Authority-Analysis: v=2.4 cv=Oq2Kdwzt c=1 sm=1 tr=0 ts=6226413d a=ApxJNpeYhEAb1aAlGBBbmA==:117 a=ApxJNpeYhEAb1aAlGBBbmA==:17 a=dLZJa+xiwSxG16/P+YVxDGlgEgI=:19 a=o8Y5sQTvuykA:10:nop_rcvd_month_year a=Qbun_eYptAEA:10:endurance_base64_authed_username_1 a=2mottZ3TzAcfEraIx6QA:9 DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=tromey.com; s=default; h=Content-Type:MIME-Version:Message-ID:In-Reply-To:Date:References :Subject:Cc:To:From:Sender:Reply-To:Content-Transfer-Encoding:Content-ID: Content-Description:Resent-Date:Resent-From:Resent-Sender:Resent-To:Resent-Cc :Resent-Message-ID:List-Id:List-Help:List-Unsubscribe:List-Subscribe: List-Post:List-Owner:List-Archive; bh=OiQd9bmJK/1bRHjOOTVLJnOzNeuSIhQa++nU1UsQMww=; b=dNCJsc5PUYmQ00GUXBJIPxunYG eSmRisIcezk8tGd3ft2o74Jp1dESeL+3fEHCBMn5EbISdKKJKLnovjLOuyfV19F9T4VBJ+jlbglEl ozTYojqs7m+2g18IN0EbJlVVW; Received: from 75-166-141-253.hlrn.qwest.net ([75.166.141.253]:47640 helo=prentzel) by box5379.bluehost.com with esmtpsa (TLS1.2) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.94.2) (envelope-from ) id 1nRHBs-0047PU-AM; Mon, 07 Mar 2022 10:30:36 -0700 From: Tom Tromey To: Florian Weimer Subject: Re: How to backtrace an separate stack? References: <87sfrtakce.fsf@oldenburg.str.redhat.com> X-Attribution: Tom Date: Mon, 07 Mar 2022 10:30:35 -0700 In-Reply-To: <87sfrtakce.fsf@oldenburg.str.redhat.com> (Florian Weimer's message of "Mon, 07 Mar 2022 15:49:37 +0100") Message-ID: <87fsnt1xhg.fsf@tromey.com> User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/27.2 (gnu/linux) MIME-Version: 1.0 Content-Type: text/plain X-AntiAbuse: This header was added to track abuse, please include it with any abuse report X-AntiAbuse: Primary Hostname - box5379.bluehost.com X-AntiAbuse: Original Domain - sourceware.org X-AntiAbuse: Originator/Caller UID/GID - [47 12] / [47 12] X-AntiAbuse: Sender Address Domain - tromey.com X-BWhitelist: no X-Source-IP: 75.166.141.253 X-Source-L: No X-Exim-ID: 1nRHBs-0047PU-AM X-Source: X-Source-Args: X-Source-Dir: X-Source-Sender: 75-166-141-253.hlrn.qwest.net (prentzel) [75.166.141.253]:47640 X-Source-Auth: tom+tromey.com X-Email-Count: 2 X-Source-Cap: ZWx5bnJvYmk7ZWx5bnJvYmk7Ym94NTM3OS5ibHVlaG9zdC5jb20= X-Local-Domain: yes 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: , Cc: pedro@palves.net, Stefan Hajnoczi via Gdb , qemu-devel@nongnu.org, "Dr. David Alan Gilbert" , Stefan Hajnoczi , tom@tromey.com Errors-To: gdb-bounces+public-inbox=simark.ca@sourceware.org Sender: "Gdb" Florian> I'm a bit surprised by this. Conceptually, why would GDB need to know Florian> about stack boundaries? Is there some heuristic to detect broken Florian> frames? Yes, the infamous "previous frame inner to this frame" error message. I think this is primarily intended to detect stack trashing, but maybe it also serves to work around bad debuginfo or bugs in the unwinders. This error was disabled for cases where the GCC split stack feature is used. There's been requests to disable it in other cases as well, I think. Tom