This is the mail archive of the gdb-patches@sourceware.org mailing list for the GDB project.

Index Nav:	[Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav:	[Date Prev] [Date Next]	[Thread Prev] [Thread Next]
Other format:	[Raw text]

Re: [patch]: Remove current_gdbarch from target.c

From: Daniel Jacobowitz <drow at false dot org>
To: Ulrich Weigand <uweigand at de dot ibm dot com>
Cc: Markus Deuling <deuling at de dot ibm dot com>, GDB Patches <gdb-patches at sourceware dot org>
Date: Tue, 20 May 2008 11:26:44 -0400
Subject: Re: [patch]: Remove current_gdbarch from target.c
References: <483143AE.8060704@de.ibm.com> <200805201516.m4KFGOwH001309@d12av02.megacenter.de.ibm.com>

On Tue, May 20, 2008 at 05:16:24PM +0200, Ulrich Weigand wrote:
> Markus Deuling wrote:
> 
> 
> > 	* target.c (target_translate_tls_address): Replace current_gdbarch by
> > 	objfile arch.
> 
> This is OK.

Is it really?  What are the guarantees for the objfile architecture?

If an object is not sniffed as belonging to a particular os/abi, I
believe we won't get its tls address routine now, even when connected
to a target reporting the appropriate OS/ABI some other way or using
set arch.

This is not a big deal for Linux, since every linked object is
generally sniffable.  But I've been working with two other OS's
recently where our dependence on sniffers is a problem; neither
Symbian OS nor DICOS has clear markings.

-- 
Daniel Jacobowitz
CodeSourcery

Follow-Ups:
- Re: [patch]: Remove current_gdbarch from target.c
  - From: Ulrich Weigand

References:
- [patch]: Remove current_gdbarch from target.c
  - From: Markus Deuling
- Re: [patch]: Remove current_gdbarch from target.c
  - From: Ulrich Weigand

Index Nav:	[Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav:	[Date Prev] [Date Next]	[Thread Prev] [Thread Next]