From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 6813 invoked by alias); 26 Jun 2007 14:52:46 -0000 Received: (qmail 6805 invoked by uid 22791); 26 Jun 2007 14:52:45 -0000 X-Spam-Check-By: sourceware.org Received: from smtp1.rug.nl (HELO smtp1.rug.nl) (129.125.50.11) by sourceware.org (qpsmtpd/0.31) with SMTP; Tue, 26 Jun 2007 14:52:40 +0000 Received: from smtp1.rug.nl ([129.125.50.11]) by smtp1.rug.nl (SMSSMTP 4.1.0.19) with SMTP id M2007062616523703742 for ; Tue, 26 Jun 2007 16:52:37 +0200 Received: from [129.125.177.235] (theobio36.biol.rug.nl [129.125.177.235]) by smtp1.rug.nl (8.12.11.20060308/8.12.11) with ESMTP id l5QEqbU8019706; Tue, 26 Jun 2007 16:52:37 +0200 (MEST) Message-ID: <46812835.5010509@rug.nl> Date: Tue, 26 Jun 2007 14:52:00 -0000 From: Bram Kuijper User-Agent: Thunderbird 2.0.0.4 (X11/20070618) MIME-Version: 1.0 To: Bram Kuijper , gdb@sourceware.org Subject: Re: "failed to find valid object file", but which object file? (using static libraries) References: <4680D290.8020303@rug.nl> <20070626112126.GA19752@caradoc.them.org> <4680F947.9000700@rug.nl> <20070626113632.GA20208@caradoc.them.org> <4680FDDE.9030607@rug.nl> <20070626121031.GA22314@caradoc.them.org> In-Reply-To: <20070626121031.GA22314@caradoc.them.org> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Spam-Report: Spam detection software on "smtp1.rug.nl". Questions: postmaster@rug.nl Content analysis details: (-4.0 points, 4.0 required) SUBJ_HAS_SPACES=0.973,USER_IN_WHITELIST=-5 ____ X-IsSubscribed: yes Mailing-List: contact gdb-help@sourceware.org; run by ezmlm Precedence: bulk List-Id: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: gdb-owner@sourceware.org X-SW-Source: 2007-06/txt/msg00300.txt.bz2 Filed a bug, see what comes from it. https://bugs.launchpad.net/ubuntu/+source/gdb/+bug/122314 Daniel Jacobowitz wrote: > On Tue, Jun 26, 2007 at 01:51:58PM +0200, Bram Kuijper wrote: >>> No, you should figure out why GDB has failed :-) You'd have to debug >>> it, though. The error message indicates that either reading from >>> memory has failed or else the image found there was surprising >>> somehow. If you run with "set debug target 1", do any errors show up? >> it was quite some output, so I put it on pastebin.com: >> >> http://pastebin.com/936686 > > > child:target_xfer_partial (1, (null), 0xbff40994, 0x0, 0xffffe000, 52) = -1 > target_terminal_ours () > Failed to read a valid object file image from memory. > > 0xffffe000 is the traditional address of the vDSO. I don't know why > you couldn't read from it; you may wish to report this to Ubuntu. >