From: "Ramana Radhakrishnan" <ramana.radhakrishnan@codito.com>
To: "Rohit Grover" <rgrover@panasas.com>
Cc: gdb@sources.redhat.com
Subject: Re: how does gdb extract symbol table information from binary files?
Date: Fri, 16 Jul 2004 17:59:00 -0000 [thread overview]
Message-ID: <3089.203.145.159.40.1090001565.squirrel@203.145.159.40> (raw)
> Hello,
>
> Could someone please help me understand how gdb fishes symbol table
> information when asked to print a struct value? I tried working my way
> down print_command_1(), but didn't succeed.
Or do you mean type information ? The symbol information can minimally be
gleaned from the ELF headers. The type information and the association of
a variable / address with a type would come from the debug info in
whatever form that might be.
cheers
Ramana
----
Ramana Radhakrishnan
GNU Tools
(codito ergo sum) www.codito.com
next reply other threads:[~2004-07-16 17:57 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-07-16 17:59 Ramana Radhakrishnan [this message]
2004-07-16 20:08 ` Charlls Quarra
-- strict thread matches above, loose matches on Subject: below --
2004-07-15 23:43 Rohit Grover
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=3089.203.145.159.40.1090001565.squirrel@203.145.159.40 \
--to=ramana.radhakrishnan@codito.com \
--cc=gdb@sources.redhat.com \
--cc=rgrover@panasas.com \
/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