Mirror of the gdb mailing list
 help / color / mirror / Atom feed
From: Daniel Jacobowitz <drow@false.org>
To: "H. J. Lu" <hjl@lucon.org>
Cc: GDB <gdb@sources.redhat.com>
Subject: Re: Does gdb support weak/normal symbols?
Date: Mon, 16 Jan 2006 15:58:00 -0000	[thread overview]
Message-ID: <20060116155846.GA3580@nevyn.them.org> (raw)
In-Reply-To: <20060116154754.GA10336@lucon.org>

On Mon, Jan 16, 2006 at 07:47:54AM -0800, H. J. Lu wrote:
> On Sun, Jan 15, 2006 at 08:49:04PM -0500, Daniel Jacobowitz wrote:
> > On Sun, Jan 15, 2006 at 04:48:31PM -0800, H. J. Lu wrote:
> > > foo in weak.c isn't in the symbol table. But gdb sets the breakpoint
> > > of foo on it. Shouldn't gdb be clever enough to know to check the
> > > other one?
> > 
> > GDB uses the debug information in preference to the ELF symbol table. 
> > That one says this is a definition of foo.
> > 
> > Eventually "break foo" will breakpoint both of them.
> 
> What did you mean by "Eventually"? Were you saying that it was a bug
> and would be fixed in the future? Is anyone working on it? I'd like
> to help.

Please read the archives for the last few days.  This is covered by the
same general problem description as "break FILE:LINE" - you have asked
for an ambiguous breakpoint, and instead of properly placing multiple
breakpoints or prompting GDB has picked one at random.

-- 
Daniel Jacobowitz
CodeSourcery


  reply	other threads:[~2006-01-16 15:58 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-01-16  0:48 H. J. Lu
2006-01-16  1:49 ` Daniel Jacobowitz
2006-01-16 15:48   ` H. J. Lu
2006-01-16 15:58     ` Daniel Jacobowitz [this message]
2006-01-16 18:11       ` H. J. Lu
2006-01-16 18:30         ` Daniel Jacobowitz
2006-01-16 18:32           ` H. J. Lu
2006-01-16 18:53             ` Daniel Jacobowitz
2006-01-16 18:35               ` 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=20060116155846.GA3580@nevyn.them.org \
    --to=drow@false.org \
    --cc=gdb@sources.redhat.com \
    --cc=hjl@lucon.org \
    /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