[PATCH 5/9] Add a helper function to resolve TLS variable addresses for FreeBSD.

[John Baldwin]

On 1/22/19 10:42 AM, John Baldwin wrote:
> The fbsd_get_thread_local_address function accepts the base address of
> a thread's DTV array and the base address of an object file's link map
> and uses this to compute a TLS variable's address.  FreeBSD
> architectures use an architecture-specific method to determine the
> address of the DTV array pointer and call this helper function to
> perform the rest of the address calculation.
> 
> 	* fbsd-tdep.c (fbsd_pspace_data_handle): New variable.
> 	(struct fbsd_pspace_data): New type.
> 	(get_fbsd_pspace_data, fbsd_pspace_data_cleanup)
> 	(fbsd_read_integer_by_name, fbsd_fetch_rtld_offsets)
> 	(fbsd_get_tls_index, fbsd_get_thread_local_address): New function.
> 	(_initialize_fbsd_tdep): Initialize 'fbsd_pspace_data_handle'.
> 	* fbsd-tdep.c (fbsd_get_thread_local_address): New prototype.
> ---
>  gdb/ChangeLog   |  10 ++++
>  gdb/fbsd-tdep.c | 146 ++++++++++++++++++++++++++++++++++++++++++++++++
>  gdb/fbsd-tdep.h |  10 ++++
>  3 files changed, 166 insertions(+)
> 
> diff --git a/gdb/fbsd-tdep.c b/gdb/fbsd-tdep.c
> index d971d3a653..2e0f72d17b 100644
> --- a/gdb/fbsd-tdep.c
> +++ b/gdb/fbsd-tdep.c
> +
> +/* Lookup offsets of fields in the runtime linker's 'Obj_Entry'
> +   structure needed to determine the TLS index of an object file.  */
> +
> +static void
> +fbsd_fetch_rtld_offsets (struct gdbarch *gdbarch, struct fbsd_pspace_data *data)
> +{
> +  TRY
> +    {
> +      /* Fetch offsets from debug symbols in rtld.  */
> +      data->off_linkmap = parse_and_eval_long ("&((Obj_Entry *)0)->linkmap");
> +      data->off_tlsindex = parse_and_eval_long ("&((Obj_Entry *)0)->tlsindex");
> +      data->rtld_offsets_valid = true;
> +      return;

I'm not really happy about using parse_and_eval_long with an open-coded
equivalent of offsetof() here.  It seems we don't already have existing
functionality for this though?  I think I could use 'lookup_struct' to find
the 'struct type *' for 'Obj_Entry', but if I used 'lookup_struct_elt_type'
to get the type of an element that doesn't give me anything that has the
offset.  We could perhaps instead add a new function 'lookup_struct_elt_offset'
that took the element name as a string and figured out the offset.  We could
then use this to provide an 'offsetof' builtin for the C language perhaps.
However, I suspect that lookup_struct_elt_offset would have to invoke a
language-specific function to do the actual computation (just as ptype /o
handling is language-specific).

-- 
John Baldwin

                                                                           Â