This is the mail archive of the
gdb-patches@sourceware.org
mailing list for the GDB project.
Re: [patch] [VLA 2/2] Interpret FIELD_LOC_KIND_DWARF_BLOCK fields
- From: Daniel Jacobowitz <drow at false dot org>
- To: Ulrich Weigand <uweigand at de dot ibm dot com>
- Cc: Jan Kratochvil <jan dot kratochvil at redhat dot com>, gdb-patches at sourceware dot org, Joel Brobecker <brobecker at adacore dot com>, Jim Blandy <jimb at red-bean dot com>, Tobias Burnus <burnus at net-b dot de>
- Date: Mon, 19 Jan 2009 22:57:37 -0500
- Subject: Re: [patch] [VLA 2/2] Interpret FIELD_LOC_KIND_DWARF_BLOCK fields
- References: <20090113014122.GA27831@host0.dyn.jankratochvil.net> <200901191521.n0JFLAtI004277@d12av02.megacenter.de.ibm.com>
On Mon, Jan 19, 2009 at 04:21:10PM +0100, Ulrich Weigand wrote:
> Making this dwarf2-specific function directly callable seems to break
> the abstraction layer that "hides" specific details of any particular
> debug info formati from common code.
>
> However, I'm not sure I see a clean solution for this. Ideally, we'd
> have something like a LOC_COMPUTED with callback functions, to handle
> format-specific field_loc_kind values. But that would require adding
> a new pointer to "struct field", which I don't really like either as
> this is a quite space-critical data structure ...
What fields use this - is it specific to array bounds? If so can we
move it to a new array-specific extension to struct type?
--
Daniel Jacobowitz
CodeSourcery