This is the mail archive of the
gdb@sources.redhat.com
mailing list for the GDB project.
Re: debuginformation generated by GNAT
- From: Joel Brobecker <brobecker at gnat dot com>
- To: Roul Oldenburger <oldenburger dot roul at rheinmetall-de dot com>
- Cc: gdb at sources dot redhat dot com
- Date: Tue, 9 Dec 2003 15:09:11 -0500
- Subject: Re: debuginformation generated by GNAT
- References: <3FBA41DC.6050209@rheinmetall-de.com> <20031118185122.GD1319@gnat.com> <3FBCE28E.10807@rheinmetall-de.com> <20031120182051.GB1186@gnat.com> <3FBE277F.5020005@rheinmetall-de.com> <20031121194641.GC2498@gnat.com> <3FC2138B.5050900@rheinmetall-de.com>
> gen_siso_common_types__index___XDLU_0__2147483647
> gen_siso_common_types__bdt_spectral_description__T76s___U /* 0x88d0b6c */;
>
> Does this variable found at the given address/offset(?) holds the upper
> bound?
Yes.
> So if I say in case of such an array the actual size won't be given
> within the debugging output but only by reading for example this
> variable in order to calculate it?
Yes.
In terms of the user's perspective, the size of the array is not static,
it can not be determined at compilation time. So depending on what you
need to do, you can either print that the upper bound is unknown (in
GDB, we print ranges like this "(1 .. ?)", or you can also read the
value from memory, but then you'll need to start your program.
--
Joel