From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 32681 invoked by alias); 25 Nov 2010 16:30:49 -0000 Received: (qmail 32652 invoked by uid 22791); 25 Nov 2010 16:30:43 -0000 X-SWARE-Spam-Status: No, hits=-2.1 required=5.0 tests=AWL,BAYES_00 X-Spam-Check-By: sourceware.org Received: from rock.gnat.com (HELO rock.gnat.com) (205.232.38.15) by sourceware.org (qpsmtpd/0.43rc1) with ESMTP; Thu, 25 Nov 2010 16:30:31 +0000 Received: from localhost (localhost.localdomain [127.0.0.1]) by filtered-rock.gnat.com (Postfix) with ESMTP id 0F2BD2BAC79; Thu, 25 Nov 2010 11:30:30 -0500 (EST) Received: from rock.gnat.com ([127.0.0.1]) by localhost (rock.gnat.com [127.0.0.1]) (amavisd-new, port 10024) with LMTP id nfmI4SivkT51; Thu, 25 Nov 2010 11:30:29 -0500 (EST) Received: from joel.gnat.com (localhost.localdomain [127.0.0.1]) by rock.gnat.com (Postfix) with ESMTP id CC7672BAC08; Thu, 25 Nov 2010 11:30:29 -0500 (EST) Received: by joel.gnat.com (Postfix, from userid 1000) id 855A31457E1; Thu, 25 Nov 2010 08:30:22 -0800 (PST) Date: Thu, 25 Nov 2010 16:30:00 -0000 From: Joel Brobecker To: Mark Kettenis Cc: pierre.muller@ics-cnrs.unistra.fr, gdb-patches@sourceware.org Subject: Re: [RFC] Improve amd64 prologue analysis Message-ID: <20101125163022.GI2634@adacore.com> References: <001701cb84ea$6883c170$398b4450$@muller@ics-cnrs.unistra.fr> <20101118172209.GE2634@adacore.com> <004201cb87c1$dab95cd0$902c1670$@muller@ics-cnrs.unistra.fr> <201011242118.oAOLIqZI030918@glazunov.sibelius.xs4all.nl> <20101124221451.GE2634@adacore.com> <20101124222555.GG2634@adacore.com> <201011251338.oAPDck2Y013525@glazunov.sibelius.xs4all.nl> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <201011251338.oAPDck2Y013525@glazunov.sibelius.xs4all.nl> User-Agent: Mutt/1.5.20 (2009-06-14) Mailing-List: contact gdb-patches-help@sourceware.org; run by ezmlm Precedence: bulk List-Id: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: gdb-patches-owner@sourceware.org X-SW-Source: 2010-11/txt/msg00429.txt.bz2 > > One last bit of information - which I got second hand, but hopefully > > accurate. I think that the GCC team is on its way to generating the > > unwinding info in that format, rather than the usual DWARF-based > > eh_frame/debug_frame. So the Microsoft format should become the default > > even for code generated by GCC... So eventually, I think we are going > > to need to add an unwinder for that, even for GCC code. > > I certainly hope you're wrong here, since it would mean a massive ABI > break on platforms currently using .eh_frame, and presumably would be > x86-specific. I should have said that this is only relevant to x86_64-windows. All other platforms will continue to use the usual eh_frame, of course. -- Joel