From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 14593 invoked by alias); 24 Nov 2010 22:17:08 -0000 Received: (qmail 14585 invoked by uid 22791); 24 Nov 2010 22:17:08 -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; Wed, 24 Nov 2010 22:17:04 +0000 Received: from localhost (localhost.localdomain [127.0.0.1]) by filtered-rock.gnat.com (Postfix) with ESMTP id 66F3B2BACA9; Wed, 24 Nov 2010 17:17:02 -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 NciO85jYujZg; Wed, 24 Nov 2010 17:17:02 -0500 (EST) Received: from joel.gnat.com (localhost.localdomain [127.0.0.1]) by rock.gnat.com (Postfix) with ESMTP id 3A1392BACA8; Wed, 24 Nov 2010 17:17:02 -0500 (EST) Received: by joel.gnat.com (Postfix, from userid 1000) id 4D8DE1457E1; Wed, 24 Nov 2010 14:16:56 -0800 (PST) Date: Wed, 24 Nov 2010 22:17: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: <20101124221656.GF2634@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> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <201011242118.oAOLIqZI030918@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/msg00418.txt.bz2 > Now I suspect that 64-bit Windows, given its utterly retarded IL32P64 > model, doesn't follow that ABI. Therefore my suggestion would be to > only use this code on Windows. BTW: We could do that (only use the code on Windows), but I would think that this is already the case de facto: Since we're supposed to always have DWARF unwinding info on platforms such as GNU/Linux, should this code ever trigger? -- Joel