From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 27756 invoked by alias); 31 Mar 2013 05:48:51 -0000 Mailing-List: contact gdb-help@sourceware.org; run by ezmlm Precedence: bulk List-Id: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: gdb-owner@sourceware.org Received: (qmail 27736 invoked by uid 89); 31 Mar 2013 05:48:38 -0000 X-Spam-SWARE-Status: No, score=-7.0 required=5.0 tests=AWL,BAYES_00,KHOP_RCVD_UNTRUST,RCVD_IN_DNSWL_HI,RCVD_IN_HOSTKARMA_W,RP_MATCHES_RCVD,SPF_HELO_PASS autolearn=ham version=3.3.1 Received: from mx1.redhat.com (HELO mx1.redhat.com) (209.132.183.28) by sourceware.org (qpsmtpd/0.84/v0.84-167-ge50287c) with ESMTP; Sun, 31 Mar 2013 05:48:35 +0000 Received: from int-mx10.intmail.prod.int.phx2.redhat.com (int-mx10.intmail.prod.int.phx2.redhat.com [10.5.11.23]) by mx1.redhat.com (8.14.4/8.14.4) with ESMTP id r2V5mUa6002955 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK); Sun, 31 Mar 2013 01:48:30 -0400 Received: from host2.jankratochvil.net (ovpn-116-39.ams2.redhat.com [10.36.116.39]) by int-mx10.intmail.prod.int.phx2.redhat.com (8.14.4/8.14.4) with ESMTP id r2V5mPQZ009103 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES128-SHA bits=128 verify=NO); Sun, 31 Mar 2013 01:48:29 -0400 Date: Sun, 31 Mar 2013 05:48:00 -0000 From: Jan Kratochvil To: Richard Smith Cc: gdb@sourceware.org Subject: Re: Backtraces broken on i386 by unorthodox encoding of push %ebp Message-ID: <20130331054825.GA2537@host2.jankratochvil.net> References: <20130330195008.GA11994@host2.jankratochvil.net> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.5.21 (2010-09-15) X-IsSubscribed: yes X-SW-Source: 2013-03/txt/msg00089.txt.bz2 On Sat, 30 Mar 2013 22:02:55 +0100, Richard Smith wrote: > Yes, you're right, I could quite easily. But a design criterion for > this project is that it is easy for third-parties to produce > backtraces from production code (i.e. once debugging information has > been stripped). It should be in .eh_frame - which is also used for exceptions unwinding if an exception is thrown through this frame. .eh_frame is runtime information, it is in a mapped segment and never stripped. Jan