From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 20306 invoked by alias); 29 Sep 2006 19:33:50 -0000 Received: (qmail 20294 invoked by uid 22791); 29 Sep 2006 19:33:50 -0000 X-Spam-Check-By: sourceware.org Received: from nile.gnat.com (HELO nile.gnat.com) (205.232.38.5) by sourceware.org (qpsmtpd/0.31) with ESMTP; Fri, 29 Sep 2006 19:33:47 +0000 Received: from localhost (localhost [127.0.0.1]) by filtered-nile.gnat.com (Postfix) with ESMTP id 6968D48CBB6; Fri, 29 Sep 2006 15:33:45 -0400 (EDT) Received: from nile.gnat.com ([127.0.0.1]) by localhost (nile.gnat.com [127.0.0.1]) (amavisd-new, port 10024) with LMTP id 08794-01-3; Fri, 29 Sep 2006 15:33:45 -0400 (EDT) Received: from takamaka.act-europe.fr (unknown [70.71.0.212]) by nile.gnat.com (Postfix) with ESMTP id E5B2A48CBAE; Fri, 29 Sep 2006 15:33:44 -0400 (EDT) Received: by takamaka.act-europe.fr (Postfix, from userid 507) id 1864C47F00; Fri, 29 Sep 2006 12:33:44 -0700 (PDT) Date: Fri, 29 Sep 2006 19:33:00 -0000 From: Joel Brobecker To: gdb@sourceware.org, Mark Kettenis Subject: Re: dwarf2-frame vs set_loc Message-ID: <20060929193344.GD1626@adacore.com> References: <20060928224245.GA21955@nevyn.them.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20060928224245.GA21955@nevyn.them.org> User-Agent: Mutt/1.4i Mailing-List: contact gdb-help@sourceware.org; run by ezmlm Precedence: bulk List-Subscribe: List-Archive: List-Post: List-Help: , Sender: gdb-owner@sourceware.org X-SW-Source: 2006-09/txt/msg00191.txt.bz2 > GCC was temporarily changed to use DW_CFA_set_loc at the start of FDEs. > I believe that change has now been backed out again; it was wrong (and > partly my fault). But Debian happened to pick up a snapshot containing > that patch and it caused a couple of GDB test failures. At least one, > anyway, I'm not sure if the other two had the same cause. This is on > x86_64. It is something we also saw in GCC 4.1 and was planning on looking at this issue for ourselves too sometimes this afternoon or maybe monday (provided I don't have any other schedule change again). Interestingly, I stopped at the same place you did... Let me see if I can have a look within the next few days. Let me know if you have time earlier to look into this, so that we don't duplicate efforts. What's the status at the compiler level, by the way? Still backed out? If this is the case, I might have to work a bit harder to still be able to reproduce the problem, because the compiler I have access to is rebuilt nightly. I should have made a copy of the compiler :-/. -- Joel