From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 12795 invoked by alias); 1 May 2004 14:11:58 -0000 Mailing-List: contact gdb-help@sources.redhat.com; run by ezmlm Precedence: bulk List-Subscribe: List-Archive: List-Post: List-Help: , Sender: gdb-owner@sources.redhat.com Received: (qmail 12788 invoked from network); 1 May 2004 14:11:57 -0000 Received: from unknown (HELO mx1.redhat.com) (66.187.233.31) by sources.redhat.com with SMTP; 1 May 2004 14:11:57 -0000 Received: from int-mx1.corp.redhat.com (int-mx1.corp.redhat.com [172.16.52.254]) by mx1.redhat.com (8.12.10/8.12.10) with ESMTP id i41EBvKI026953 for ; Sat, 1 May 2004 10:11:57 -0400 Received: from localhost.redhat.com (porkchop.devel.redhat.com [172.16.58.2]) by int-mx1.corp.redhat.com (8.11.6/8.11.6) with ESMTP id i41EBuv13891; Sat, 1 May 2004 10:11:56 -0400 Received: from gnu.org (localhost [127.0.0.1]) by localhost.redhat.com (Postfix) with ESMTP id 84CFB2B9D; Sat, 1 May 2004 10:11:54 -0400 (EDT) Message-ID: <4093B02A.5040506@gnu.org> Date: Sat, 01 May 2004 14:11:00 -0000 From: Andrew Cagney User-Agent: Mozilla/5.0 (X11; U; NetBSD macppc; en-GB; rv:1.4.1) Gecko/20040217 MIME-Version: 1.0 To: Olivier Crete Cc: gdb@sources.redhat.com Subject: Re: Wierd problem with gdb 6.x and separate debug info References: <1083400741.8129.25.camel@TesterTop.tester.ca> <40939F85.7060502@gnu.org> <1083417821.8129.31.camel@TesterTop.tester.ca> In-Reply-To: <1083417821.8129.31.camel@TesterTop.tester.ca> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit X-SW-Source: 2004-05/txt/msg00003.txt.bz2 > Hi, > > On Sat, 2004-05-01 at 15:00, Andrew Cagney wrote: > >>> Look at, and run, the gdb.base/sepdebug.exp testcase. Running that will >>> at least confirm that the mechanism is working. > > > I get 2 errors. > FAIL: run until function breakpoint > FAIL: run until function breakpoint, optimized file On Red Hat's RHEL 3 system (i386) I see no failures. Do you get the other warnings (see gdb.log)? If not, then these failures are probably due to other bugs. > Both using yesterday's cvs snapshot and 6.0. > > >>> After that, it depends on the system, look at "set >>> debug-file-directory". Your system's debug directory may not match GDBs. > > > I've put the debug info in .debug/ in the same directory as the libs.. Ok, I guess it is finding the relevant files. Look in gdb.log and check exactly how objcopy is run. Andrew