From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 17080 invoked by alias); 13 Jan 2011 01:01:02 -0000 Received: (qmail 17062 invoked by uid 22791); 13 Jan 2011 01:01:01 -0000 X-SWARE-Spam-Status: No, hits=-2.3 required=5.0 tests=AWL,BAYES_00,RCVD_IN_DNSWL_LOW,T_RP_MATCHES_RCVD X-Spam-Check-By: sourceware.org Received: from g1t0027.austin.hp.com (HELO g1t0027.austin.hp.com) (15.216.28.34) by sourceware.org (qpsmtpd/0.43rc1) with ESMTP; Thu, 13 Jan 2011 01:00:56 +0000 Received: from g1t0039.austin.hp.com (g1t0039.austin.hp.com [16.236.32.45]) by g1t0027.austin.hp.com (Postfix) with ESMTP id 9347E38D35; Thu, 13 Jan 2011 01:00:53 +0000 (UTC) Received: from [16.89.92.85] (hpsje.cup.hp.com [16.89.92.85]) by g1t0039.austin.hp.com (Postfix) with ESMTP id 31DB334291; Thu, 13 Jan 2011 01:00:52 +0000 (UTC) Subject: Re: [PATCH 6/8] port GDB to ia64-hpux (native). From: Steve Ellcey Reply-To: sje@cup.hp.com To: Joel Brobecker Cc: gdb-patches@sourceware.org In-Reply-To: <20110112231604.GI2504@adacore.com> References: <1293511386-7384-7-git-send-email-brobecker@adacore.com> <201101112314.p0BNErd19061@lucas.cup.hp.com> <20110112231604.GI2504@adacore.com> Content-Type: text/plain; charset="UTF-8" Date: Thu, 13 Jan 2011 05:13:00 -0000 Message-ID: <1294880224.21802.182.camel@hpsje.cup.hp.com> Mime-Version: 1.0 Content-Transfer-Encoding: 7bit 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: 2011-01/txt/msg00287.txt.bz2 On Wed, 2011-01-12 at 18:16 -0500, Joel Brobecker wrote: > I'm doing the final checks before committing the corrected version. > But something caught my attention: > > > I then ran the testsuite and here are the base results. > > > > gdb.base1 results: > > You are getting considerably more failures than I am. I think > they could be explain by 2 factors (but I am only guessing): > - I use GNU libunwind (or a modified version of 0.98); > That makes a real difference in our case, compared to using > the system libunwind. I am using the system libunwind. > - the 32bit mode might make a difference as well; not sure. I was wondering if this was an issue or not, I tried debugging the latest GCC using the GDB I built and I couldn't get decent backtraces. I thought it might be a 32/64 bit issue, but perhaps it is the system libunwind. Steve Ellcey sje@cup.hp.com