From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 25124 invoked by alias); 5 Feb 2008 22:29:57 -0000 Received: (qmail 25113 invoked by uid 22791); 5 Feb 2008 22:29:56 -0000 X-Spam-Status: No, hits=-2.1 required=5.0 tests=AWL,BAYES_00 X-Spam-Check-By: sourceware.org Received: from wildebeest.demon.nl (HELO gnu.wildebeest.org) (83.160.170.119) by sourceware.org (qpsmtpd/0.31) with ESMTP; Tue, 05 Feb 2008 22:29:27 +0000 Received: from dijkstra.wildebeest.org ([192.168.1.29]) by gnu.wildebeest.org with esmtp (Exim 4.63) (envelope-from ) id 1JMWI8-0004yc-02 for frysk@sourceware.org; Tue, 05 Feb 2008 23:29:24 +0100 Subject: Merged new upstream libunwind code From: Mark Wielaard To: frysk@sourceware.org Content-Type: text/plain Date: Tue, 05 Feb 2008 22:29:00 -0000 Message-Id: <1202250563.19234.20.camel@dijkstra.wildebeest.org> Mime-Version: 1.0 X-Mailer: Evolution 2.12.3 (2.12.3-1.fc8) Content-Transfer-Encoding: 7bit X-Spam-Score: -4.4 (----) X-IsSubscribed: yes Mailing-List: contact frysk-help@sourceware.org; run by ezmlm Precedence: bulk List-Id: List-Subscribe: List-Post: List-Help: , Sender: frysk-owner@sourceware.org X-SW-Source: 2008-q1/txt/msg00053.txt.bz2 Hi, Since there was a huge commit in upstream libunwind that overlaps a bit with some of our patches I imported it and merged it with our code. It does also contains two of our patches so some of the divergence has come down again. It contains some support for local debug_frame parsing support. Unfortunately that bites our remote debug_frame parsing a bit. I added comments where our approach is different from upstream or the assumptions don't hold for our remote case. I didn't try use some of the new parsing code introduced since our current approach works just fine for the remote case. It also contains support for ARM and MIPS. This isn't being compiled yet in our tree (only x86, x86_64, ppc and ppc64 is). Tested on x86 and x86_64 and no regressions in our testsuite. But there is one extra failure in the libunwind testsuite (a local failure) that needs investigating (you normally won't see it unless you configure --enable-check-libunwind --enable-debug). Cheers, Mark