From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 27764 invoked by alias); 27 May 2005 04:48:06 -0000 Mailing-List: contact insight-help@sources.redhat.com; run by ezmlm Precedence: bulk List-Subscribe: List-Archive: List-Post: List-Help: , Sender: insight-owner@sources.redhat.com Received: (qmail 27663 invoked by uid 22791); 27 May 2005 04:47:51 -0000 Received: from sccrmhc13.comcast.net (HELO sccrmhc13.comcast.net) (204.127.202.64) by sourceware.org (qpsmtpd/0.30-dev) with ESMTP; Fri, 27 May 2005 04:47:51 +0000 Received: from [10.0.1.2] (c-24-61-199-96.hsd1.nh.comcast.net[24.61.199.96]) by comcast.net (sccrmhc13) with SMTP id <2005052704474901600g0j3fe>; Fri, 27 May 2005 04:47:49 +0000 User-Agent: Microsoft-Entourage/11.1.0.040913 Date: Fri, 27 May 2005 04:48:00 -0000 Subject: Re: [patch] updates gdbtk to use lbasename() do to shared lib header tweaks. From: Paul Schlie To: Keith Seitz CC: "insight@sources.redhat.com" Message-ID: In-Reply-To: <1117157462.4456.117.camel@lindt.uglyboxes.com> Mime-version: 1.0 Content-type: text/plain; charset="US-ASCII" Content-transfer-encoding: 7bit X-SW-Source: 2005-q2/txt/msg00101.txt.bz2 > From: Keith Seitz >> On Thu, 2005-05-26 at 19:09 -0400, Paul Schlie wrote: >> (patch enclosed as an attachment, so don't know if it's visible on boards) > > Hmm. For some reason, I could not apply your patch. Goofy. Fortunately, > it was simple enough. > > I have also take the opportunity to remove a few other compiler warnings > stemming from some gdb "API" changes from char* to gdb_byte*. > > I tried to run this through the testsuite, but I see that varobj.c is > throwing an internal error trying to run c_variable.exp. :-( Thank you. With respect to the test-suite failure, I'm embarrassed to admit that I've never actually run it, as for some reason which I haven't looked close enough to know why, it's not being built by default when I configure and build the entire source tree (so correspondingly have never run it), but things seem to be ok (but haven't applied your latest tweaks yet which should only help), but suspect its possible something subtle is wrong that the test-suite is catching that I haven't seen or noticed?