From: Roul Oldenburger <oldenburger.roul@rheinmetall-de.com>
To: gdb@sources.redhat.com
Subject: how does gdb read type descriptions for structures
Date: Fri, 22 Aug 2003 08:27:00 -0000 [thread overview]
Message-ID: <3F45D472.2070407@rheinmetall-de.com> (raw)
Hello everyone,
most time I am only using gdb and most time via ddd but I have got a
question for gdb internals.
I am trying to reconstruct type descriptions for a tree of structures
from stabs debug informations included in executables.
Using for example 'ptype my_structure' in gdb delivers me components and
types of my_structure but it looks like gdb prints part of the source
code ... or does it evaluate its symbol tables or stabs information via
BFD directly?
Furthermore I need to know the offset/address of each component of each
substructure in the structure tree ... we are using quit complex
structures.
Using 'objdump --stabs' I will get all the information/ type
descriptions I need but I hope there is another way to retrieve this
information rather than working it out from the text in .stabstr.
How does gdb does it?
Thanks for your help
Roul Oldenburger
next reply other threads:[~2003-08-22 8:27 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-08-22 8:27 Roul Oldenburger [this message]
2003-08-22 12:52 ` Daniel Jacobowitz
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=3F45D472.2070407@rheinmetall-de.com \
--to=oldenburger.roul@rheinmetall-de.com \
--cc=gdb@sources.redhat.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