public inbox for gdb-prs@sourceware.org
help / color / mirror / Atom feed
From: "pyxchina at sina dot com" <sourceware-bugzilla@sourceware.org>
To: gdb-prs@sourceware.org
Subject: [Bug symtab/12909] New: gdb fails to figure out the right symbol of function in which my kernel is currently run.
Date: Fri, 17 Jun 2011 15:33:00 -0000	[thread overview]
Message-ID: <bug-12909-4717@http.sourceware.org/bugzilla/> (raw)

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.


             reply	other threads:[~2011-06-17 15:33 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-06-17 15:33 pyxchina at sina dot com [this message]
2011-06-17 15:53 ` [Bug symtab/12909] " pyxchina at sina dot com
2011-07-06  1:55 ` qiyao at gcc dot gnu.org
2011-07-06  2:35 ` pyxchina at sina dot com
2011-07-06  2:41 ` qiyao at gcc dot gnu.org

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=bug-12909-4717@http.sourceware.org/bugzilla/ \
    --to=sourceware-bugzilla@sourceware.org \
    --cc=gdb-prs@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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).