* Symbol at the incorrect address
@ 2006-07-12 22:34 Shaun Jackman
2006-07-13 3:13 ` Daniel Jacobowitz
0 siblings, 1 reply; 2+ messages in thread
From: Shaun Jackman @ 2006-07-12 22:34 UTC (permalink / raw)
To: gdb
arm-elf-nm and arm-elf-gdb disagree about the location of symbols:
$ arm-elf-nm vmlinux |grep log_buf
01009e8c b __log_buf
01509b48 t __setup_log_buf_len_setup
01002b84 d __setup_str_log_buf_len_setup
01004cac d log_buf
01004ca8 d log_buf_len
01505908 t log_buf_len_setup
$ arm-elf-gdb vmlinux
GNU gdb 6.5.50.20060627-cvs
...
(gdb) p &__log_buf
$1 = (char (*)[16384]) 0x201138c
(gdb) p &log_buf
$2 = (char **) 0x2004cac
It appears as if the section address is being added to the symbol address twice.
Please cc me in your reply. Thanks,
Shaun
binutils 2.17
gcc 4.2.0 20060629
gdb 6.5.50.20060627-cvs
linux 2.6.14.7
configured for XIP
.text in flash at 0x1500000
.data in RAM at 0x1000000
^ permalink raw reply [flat|nested] 2+ messages in thread
* Re: Symbol at the incorrect address
2006-07-12 22:34 Symbol at the incorrect address Shaun Jackman
@ 2006-07-13 3:13 ` Daniel Jacobowitz
0 siblings, 0 replies; 2+ messages in thread
From: Daniel Jacobowitz @ 2006-07-13 3:13 UTC (permalink / raw)
To: Shaun Jackman; +Cc: gdb
On Wed, Jul 12, 2006 at 04:34:18PM -0600, Shaun Jackman wrote:
> It appears as if the section address is being added to the symbol address
> twice.
Yes, it does.
Sorry, I'm not sure what else you want us to say! There's no
information in this report except that yes, something appears to be
wrong. It should be relatively straightforward to either produce a
small test case, or else debug GDB to see what has happened.
--
Daniel Jacobowitz
CodeSourcery
^ permalink raw reply [flat|nested] 2+ messages in thread
end of thread, other threads:[~2006-07-13 3:13 UTC | newest]
Thread overview: 2+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2006-07-12 22:34 Symbol at the incorrect address Shaun Jackman
2006-07-13 3:13 ` Daniel Jacobowitz
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox