Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: "Ulrich Weigand" <uweigand@de.ibm.com>
To: drow@false.org (Daniel Jacobowitz)
Cc: deuling@de.ibm.com (Markus Deuling),
	        gdb-patches@sourceware.org (GDB Patches)
Subject: Re: [patch]: Remove current_gdbarch from target.c
Date: Tue, 20 May 2008 18:38:00 -0000	[thread overview]
Message-ID: <200805201642.m4KGg3k6030194@d12av02.megacenter.de.ibm.com> (raw)
In-Reply-To: <20080520152644.GA30512@caradoc.them.org> from "Daniel Jacobowitz" at May 20, 2008 11:26:44 AM

Daniel Jacobowitz wrote:
> 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?

Well, the general idea is that objfile archiecture can / should be
used for properties that depend solely on the objfile, and not on
properties of a running target.  This currently includes mostly
things like builtin types and basic ABI properties, but also e.g.
convert_from_func_ptr_addr.

I would have considered fetch_tls_load_module_address to be of
the same type.  But on second thought, that may not really be true
-- the svr4_fetch_objfile_link_map implementation of it does hook
into the overall shared library code, which is dependent on the
target ...

Markus, please do not apply this patch for now; we'll need to 
think of another solution (probably together with the question
what gdbarch the shared library subsystem should be using).

> 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.

That would be true.

> 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.

Hmm.  Non-sniffable objects are somewhat of a problem anyway.
Maybe we need a way to at least override (manually?) the OSABI
that is used for non-sniffable objects ...

Bye,
Ulrich

-- 
  Dr. Ulrich Weigand
  GNU Toolchain for Linux on System z and Cell BE
  Ulrich.Weigand@de.ibm.com


-- 
  Dr. Ulrich Weigand
  GNU Toolchain for Linux on System z and Cell BE
  Ulrich.Weigand@de.ibm.com


  reply	other threads:[~2008-05-20 16:43 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-05-19 15:19 Markus Deuling
2008-05-20 17:04 ` Ulrich Weigand
2008-05-20 17:53   ` Daniel Jacobowitz
2008-05-20 18:38     ` Ulrich Weigand [this message]
2008-05-20 18:39       ` Daniel Jacobowitz

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=200805201642.m4KGg3k6030194@d12av02.megacenter.de.ibm.com \
    --to=uweigand@de.ibm.com \
    --cc=deuling@de.ibm.com \
    --cc=drow@false.org \
    --cc=gdb-patches@sourceware.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox