Mirror of the gdb mailing list
 help / color / mirror / Atom feed
From: Daniel Jacobowitz <drow@false.org>
To: Greg Law <greglaw@greglaw.net>
Cc: gdb@sourceware.org
Subject: Re: decode_variable's use of not_found_ptr
Date: Sun, 23 Apr 2006 15:57:00 -0000	[thread overview]
Message-ID: <20060422213607.GA14401@nevyn.them.org> (raw)
In-Reply-To: <4449E3F8.3020408@greglaw.net>

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?  This message has been
around for as long as I can remember (which isn't to say that it
shouldn't be fixed).  The pending_bp and not_found_ptr stuff is much
more recent and for a different situation.

-- 
Daniel Jacobowitz
CodeSourcery


  parent reply	other threads:[~2006-04-22 21:36 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-04-22 13:00 Greg Law
2006-04-22 16:32 ` Dave Korn
2006-04-22 21:21   ` Dave Korn
2006-04-22 21:36   ` Greg Law
2006-04-23 10:22     ` Nick Roberts
2006-04-23 15:57 ` Daniel Jacobowitz [this message]
2006-04-24  6:05   ` Greg Law
2006-04-24  6:13     ` Daniel Jacobowitz

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20060422213607.GA14401@nevyn.them.org \
    --to=drow@false.org \
    --cc=gdb@sourceware.org \
    --cc=greglaw@greglaw.net \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox