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 01:49:00 -0000 [thread overview]
Message-ID: <20060116014904.GA20402@nevyn.them.org> (raw)
In-Reply-To: <20060116004831.GA1186@lucon.org>
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.
--
Daniel Jacobowitz
CodeSourcery
next prev parent reply other threads:[~2006-01-16 1:49 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 [this message]
2006-01-16 15:48 ` H. J. Lu
2006-01-16 15:58 ` Daniel Jacobowitz
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=20060116014904.GA20402@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