From: Fabian Cenedese <Cenedese@indel.ch>
To: gdb@sourceware.org
Subject: Wrong source location in symbols
Date: Mon, 11 Dec 2006 10:16:00 -0000 [thread overview]
Message-ID: <5.2.0.9.1.20061211104829.0186dcc0@NT_SERVER> (raw)
Hi
I seem to have a problem with the code loaction of symbols.
gdb 6.5, gcc 4.1.0, compiled for ppc-eabi, running on WinXP
Here's a snippet from the generated map file:
.text 0x0000f6f4 0x41c N:/Indel-PPC/Tests/gccext3/bin41/CTaskTemplateClass.603
0x0000fa28 _TASK_CLASS_NAME_::_TASK_CLASS_NAME_(char*)
...(snip)...
.text 0x00097bfc 0x14 N:/IMD/Lib41/libnosys.a(write.o)
0x00097bfc write
.ctors 0x00097c10 0x98
...(snip)...
.dtors 0x00097ca8 0x10
...(snip)...
.got
0x00097cb8 PROVIDE (__STARTUP_BEGIN, .)
.startup 0x00097cb8 0x12320
*(.startup)
.startup 0x00097cb8 0x6c N:/Indel-PPC/Tests/gccext3/bin41/CTaskTemplateClass.603
0x00097cb8 _INI_1000__TASK_CLASS_NAME_()
But when I dump the symbol tables I get this:
[1001] T 0xeb20 _ZN17_TASK_CLASS_NAME_6ActionEv section .text _TASK_CLASS_NAME_::Action() write.c
[1002] T 0xebdc _ZN17_TASK_CLASS_NAME_D0Ev section .text _TASK_CLASS_NAME_::~_TASK_CLASS_NAME_() write.c
...(snip)...
[3549] B 0x98d44 Reg_INI_0101_INOS_TGT section .bss write.c
[3550] B 0x98d50 Reg_INI_0145_INOS_TGT section .bss write.c
[3551] B 0x98d5c Reg_INI_0205_INOS_TGT section .bss write.c
[3552] B 0x98d68 Reg_INI_0160_INOS_TGT section .bss write.c
...(snip)...
[3567] T 0x99bec _Z27_INI_1000__TASK_CLASS_NAME_v section .startup _INI_1000__TASK_CLASS_NAME_() write.c
[3575] T 0x9a530 _Z18_INI_0002_INCO_NETv section .startup _INI_0002_INCO_NET() write.c
[3576] T 0x9a5fc _Z18_INI_0150_INCO_NETv section .startup _INI_0150_INCO_NET() write.c
[3577] T 0x9a744 _Z27_INI_0002_CSAMDeviceSioLoadv section .startup _INI_0002_CSAMDeviceSioLoad() write.c
No matter where they are defined, the symbols get as location the (wrong)
file write.c, so the last valid file from the .text section. I tried with both
-gstabs or -gdwarf-2, but that didn't change anything. I also tried with
forward and back slashes in the paths of the compiled files, no luck.
Where's the code in gdb that would set these locations?
Thanks
bye Fabi
next reply other threads:[~2006-12-11 10:16 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-12-11 10:16 Fabian Cenedese [this message]
2006-12-11 13:41 ` Daniel Jacobowitz
2006-12-11 16:49 ` Fabian Cenedese
2006-12-11 16:50 ` Daniel Jacobowitz
2006-12-12 16:39 ` Fabian Cenedese
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=5.2.0.9.1.20061211104829.0186dcc0@NT_SERVER \
--to=cenedese@indel.ch \
--cc=gdb@sourceware.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