Mirror of the gdb mailing list
 help / color / mirror / Atom feed
From: Daniel Jacobowitz <drow@mvista.com>
To: Roul Oldenburger <oldenburger.roul@rheinmetall-de.com>
Cc: gdb@sources.redhat.com
Subject: Re: how does gdb read type descriptions for structures
Date: Fri, 22 Aug 2003 12:52:00 -0000	[thread overview]
Message-ID: <20030822125211.GA17380@nevyn.them.org> (raw)
In-Reply-To: <3F45D472.2070407@rheinmetall-de.com>

On Fri, Aug 22, 2003 at 10:29:38AM +0200, Roul Oldenburger wrote:
> 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?

From the debug info - i.e. the text in .stabstr.

-- 
Daniel Jacobowitz
MontaVista Software                         Debian GNU/Linux Developer


      reply	other threads:[~2003-08-22 12:52 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-08-22  8:27 Roul Oldenburger
2003-08-22 12:52 ` Daniel Jacobowitz [this message]

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=20030822125211.GA17380@nevyn.them.org \
    --to=drow@mvista.com \
    --cc=gdb@sources.redhat.com \
    --cc=oldenburger.roul@rheinmetall-de.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