This is the mail archive of the
gdb-patches@sourceware.org
mailing list for the GDB project.
Re: [PATCH 01/23] dwarf: add dwarf3 DW_OP_push_object_address opcode
- From: Joel Brobecker <brobecker at adacore dot com>
- To: Keven Boell <keven dot boell at linux dot intel dot com>
- Cc: Keven Boell <keven dot boell at intel dot com>, gdb-patches at sourceware dot org, sanimir dot agovic at intel dot com
- Date: Wed, 11 Jun 2014 15:08:15 +0200
- Subject: Re: [PATCH 01/23] dwarf: add dwarf3 DW_OP_push_object_address opcode
- Authentication-results: sourceware.org; auth=none
- References: <1401861266-6240-1-git-send-email-keven dot boell at intel dot com> <1401861266-6240-2-git-send-email-keven dot boell at intel dot com> <20140610095445 dot GA5259 at adacore dot com> <53984AE9 dot 7020200 at linux dot intel dot com>
> The address fields were introduced as DW_OP_push_object_address
> needs an object address to be pushed and this address needs to be stored
> somewhere. However, I will extend the log message why this address fields
> were introduced.
I understand this part, but the main part of my question is about
the fact that, most of the time, we manipulate "struct value" objects,
which may not represent addressable entities. For instance, let's say
I have a struct value whose type is a TYPE_CODE_ARRAY. If I need to
resolve the value's type, how should I be doing it? Perhaps, the
question in itself suggest the introduction of a function that would
take a value, and returned a value whose time is resolved?
--
Joel