From: Roul Oldenburger <oldenburger.roul@rheinmetall-de.com>
To: gdb@sources.redhat.com
Subject: debuginformation generated by GNAT
Date: Tue, 18 Nov 2003 16:01:00 -0000 [thread overview]
Message-ID: <3FBA41DC.6050209@rheinmetall-de.com> (raw)
Hello everybody,
I was looking for explanation for certain debug symbols gnat generated
from our ada sources. Joel pointed me to exp_debug.ads where most of my
questions were answered, but now I am in trouble again.
Trying to reconstruct structure type trees from debuginformation given
by binutils objdump and parsed by a program of mine ... I got stuck
where I have to compute the size of an ___XVL component (entity with
variable length) which is an array.
(objdump output)
.
.
struct gen_siso_common_types__bdt_spectral_description___XVE { /* size 4
id 1546 */
gen_siso_common_types__bdt_spectral_description__T73s *cas___XVL; /*
bitsize 32, bitpos 0 */
gen_siso_common_types__bdt_spectral_description__T75s *fas___XVL4; /*
bitsize 32, bitpos 0 */
gen_siso_common_types__bdt_spectral_description__T77s *tas___XVL4; /*
bitsize 32, bitpos 0 */
};
.
.
(corresponding ada code)
.
.
type Spectral_Table is
array (Index range <>) of Basic.Float32; -- Intensitaetsfaktoren
type Bdt_Spectral_Description is
record
Cas : Spectral_Table(1 .. Bdt_Cas_Bands); -- BDT-Spektrum CAS
Fas : Spectral_Table(1 .. Bdt_Fas_Bands); -- BDT-Spektrum FAS
Tas : Spectral_Table(1 .. Bdt_Tas_Bands); -- BDT-Spektrum TAS
end record;
.
.
When I understood exp_debug.ads right I cannot compute the size of such
array ... but the debugger surely knows it.
Can someone help?
Thanks very much
Roul
next reply other threads:[~2003-11-18 16:01 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-11-18 16:01 Roul Oldenburger [this message]
2003-11-18 18:51 ` Joel Brobecker
2003-11-20 15:49 ` Roul Oldenburger
2003-11-20 18:20 ` Joel Brobecker
2003-11-21 14:58 ` Roul Oldenburger
2003-11-21 19:46 ` Joel Brobecker
2003-11-24 14:19 ` Roul Oldenburger
2003-12-09 20:37 ` Joel Brobecker
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=3FBA41DC.6050209@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