This is the mail archive of the
gdb-prs@sourceware.org
mailing list for the GDB project.
[Bug symtab/12909] New: gdb fails to figure out the right symbol offunction in which my kernel is currently run.
- From: "pyxchina at sina dot com" <sourceware-bugzilla at sourceware dot org>
- To: gdb-prs at sourceware dot org
- Date: Fri, 17 Jun 2011 15:33:24 +0000
- Subject: [Bug symtab/12909] New: gdb fails to figure out the right symbol offunction in which my kernel is currently run.
- Auto-submitted: auto-generated
http://sourceware.org/bugzilla/show_bug.cgi?id=12909
Summary: gdb fails to figure out the right symbol of function
in which my kernel is currently run.
Product: gdb
Version: 7.2
Status: NEW
Severity: normal
Priority: P2
Component: symtab
AssignedTo: unassigned@sourceware.org
ReportedBy: pyxchina@sina.com
I am learning to write a kernel for qemu-x86.
I defined a struct variable named k_tss in one of my .c files.
I run qemu and connected it with gdb.
Then I typed "break img_entry" and "c"
Qemu stoped at img_entry(),but the gdb promted that it stoped in k_tss().
My OS : Debian-6.1
My Gcc: gcc version 4.4.5 (Debian 4.4.5-8)
My Gdb: GNU gdb (GDB) 7.2-debian
My Qemu: QEMU PC emulator version 0.12.5 (Debian 0.12.5+dfsg-3)
Please turn to attachment for all my kernel sources.
After uncompressing the tarball:
1, cd into its root directory
2, type "source config.mk"
3, type "source debug",then you'll get qemu up and connected to gdb
4, type "break img_entry" in gdb
5, type "c"
6, after the breakpoint is hitted,type "bt" and you'll see the trace
of the stack is not as it really is.All the values are correct and what looks
strange is the symbol resolved from those values.
--
Configure bugmail: http://sourceware.org/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug.