Mirror of the gdb mailing list
 help / color / mirror / Atom feed
From: Roul Oldenburger <oldenburger.roul@stn-atlas.de>
To: gdb@sources.redhat.com
Subject: questions on debug informations used by gdb
Date: Thu, 03 Jul 2003 10:39:00 -0000	[thread overview]
Message-ID: <3F04082C.4050103@stn-atlas.de> (raw)

Hello there,

I am quit new to this topic and also to this list. My apologies if I put 
this question in the wrong place.

Instances of datatypes (esp. structures and records in C and Ada) can be 
viewed using gdb ... using ddd also let me click them to view each 
single component.
What I am looking for is the information gdb is using to display the 
name and the value of a structure. More precisely I need the positions 
or lets say offsets and sizes of the structures and their components in 
memory. I am hoping to find all I need in the debug information gcc 
includes into the objectfiles.

Unfortunately I haven't found something like a list of what kind of 
information gcc includes and in what format.

Having seen gdb uses the same information I am looking for, I like to 
know where does it get it from. Probably there are functionalities in 
gdb I might use to extract the same information for my purposes?

And in case the informations I need are included, I also like to know if 
there are differences in format if compile for different platforms and 
/or different machines?

If you could help to answer my questions I would be happy!

Probably my questions seem to be basics for you, so I would be happy if 
somone could send me a link to a document or how-to, to solve them on my 
own.

Thanks a lot
Roul Oldenburger


             reply	other threads:[~2003-07-03 10:39 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-07-03 10:39 Roul Oldenburger [this message]
2003-07-03 12:10 ` 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=3F04082C.4050103@stn-atlas.de \
    --to=oldenburger.roul@stn-atlas.de \
    --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