From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 6590 invoked by alias); 8 Oct 2007 09:16:29 -0000 Received: (qmail 6582 invoked by uid 22791); 8 Oct 2007 09:16:29 -0000 X-Spam-Status: No, hits=-2.1 required=5.0 tests=AWL,BAYES_00,DK_POLICY_SIGNSOME,FORGED_RCVD_HELO 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; Mon, 08 Oct 2007 09:16:20 +0000 Received: from dijkstra.wildebeest.org ([192.168.1.29]) by gnu.wildebeest.org with esmtp (Exim 4.63) (envelope-from ) id 1Ieoij-0000jF-H8 for frysk@sourceware.org; Mon, 08 Oct 2007 11:16:18 +0200 Subject: Running libunwind tests (--enable-check-libunwind) From: Mark Wielaard To: frysk@sourceware.org Content-Type: text/plain Date: Mon, 08 Oct 2007 09:16:00 -0000 Message-Id: <1191834973.3859.8.camel@dijkstra.wildebeest.org> Mime-Version: 1.0 X-Mailer: Evolution 2.8.3 (2.8.3-2.fc6) 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: 2007-q4/txt/msg00022.txt.bz2 Hi, There is a new configure option --enable-check-libunwind that builds the embedded frysk libunwind testsuite and lets make check run it, but not for the cross-architecture versions of libunwind that we build (they are build with different flags so results aren't comparable in that case). This is handy for doing a sanity check of our copy of libunwind, that still contains a couple of patches not upstream yet. The results aren't very great (but neither is the upstream version, we are currently a little better because we have some additional tests not yet upstream), see the libunwind/README for the "known to fail" (sigh) tests. They are still useful for general platform checks since it will catch some cases where the platform vdso or glibc are missing proper CFI information. So maybe it makes sense to enable them on the autobuilder/tester just as reference. Otherwise you would only use this as sanity check when merging/importing new libunwind versions. Cheers, Mark