From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 18761 invoked by alias); 23 Apr 2006 10:22:16 -0000 Received: (qmail 18752 invoked by uid 22791); 23 Apr 2006 10:22:15 -0000 X-Spam-Check-By: sourceware.org Received: from astro.systems.pipex.net (HELO astro.systems.pipex.net) (62.241.163.6) by sourceware.org (qpsmtpd/0.31) with ESMTP; Sun, 23 Apr 2006 10:22:11 +0000 Received: from [192.168.123.106] (81-86-64-188.dsl.pipex.com [81.86.64.188]) by astro.systems.pipex.net (Postfix) with ESMTP id E097EE000149; Sun, 23 Apr 2006 11:22:08 +0100 (BST) Message-ID: <444B554B.10608@greglaw.net> Date: Mon, 24 Apr 2006 06:05:00 -0000 From: Greg Law User-Agent: Mozilla Thunderbird 1.0.7 (X11/20051013) MIME-Version: 1.0 To: Daniel Jacobowitz Cc: gdb@sourceware.org Subject: Re: decode_variable's use of not_found_ptr References: <4449E3F8.3020408@greglaw.net> <20060422213607.GA14401@nevyn.them.org> In-Reply-To: <20060422213607.GA14401@nevyn.them.org> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Mailing-List: contact gdb-help@sourceware.org; run by ezmlm Precedence: bulk List-Subscribe: List-Archive: List-Post: List-Help: , Sender: gdb-owner@sourceware.org X-SW-Source: 2006-04/txt/msg00293.txt.bz2 Daniel Jacobowitz wrote: >On Sat, Apr 22, 2006 at 09:06:16AM +0100, Greg Law wrote: > > >>Anyway, sometimes when I restart a program. I get error messages telling >>me that a breakpoint in a shared library can't be found: >> >> Error in re-setting breakpoint 2: >> Function "foo" not defined. >> Error in re-setting breakpoint 2: >> Function "foo" not defined. >> Error in re-setting breakpoint 2: >> Function "foo" not defined. >> Error in re-setting breakpoint 2: >> Function "foo" not defined. >> Error in re-setting breakpoint 2: >> Function "foo" not defined. >> Error in re-setting breakpoint 2: >> Function "foo" not defined. >> Error in re-setting breakpoint 2: >> Function "foo" not defined. >> >>I've had a quick look at the source, and the message seems to be coming >>from decode_variable() >> >> > >You've been hunting around trying to figure out how this function was >recently changed to cause this problem. I think you're looking up the >wrong tree - have you tried an earlier version? > Yes - 6.3 doesn't have this issue. g