From: Daniel Jacobowitz <drow@false.org>
To: Vinay Sridhar <vinay@linux.vnet.ibm.com>
Cc: Jan Kratochvil <jan.kratochvil@redhat.com>,
gdb-patches@sources.redhat.com, luisgpm@linux.vnet.ibm.com,
uweigand@de.ibm.com
Subject: Re: [patch] Re: Accessing tls variables across files causes a bug
Date: Wed, 06 Aug 2008 11:25:00 -0000 [thread overview]
Message-ID: <20080806112432.GA29991@caradoc.them.org> (raw)
In-Reply-To: <1218021410.13466.4.camel@vinaysridhar.in.ibm.com>
On Wed, Aug 06, 2008 at 04:46:50PM +0530, Vinay Sridhar wrote:
> We need to determine that the variable is a "tls" variable. When this is
> extern, the symbol is LOC_UNRESOLVED. So the section type from "sym" is
> not filled. Thats why I tried to determine this from the minimal symbol.
> If there is any other method of determining a variable is "tls" before
> its owning symtab is linked in, could you please inform? I used this
> section number as I could not find another way of determining this..
I imagine that Jan's right and we need to treat all unresolved symbols
this way - or be less eager about creating unresolved symbols.
--
Daniel Jacobowitz
CodeSourcery
next prev parent reply other threads:[~2008-08-06 11:25 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1217480020.4755.1.camel@vinaysridhar.in.ibm.com>
2008-08-02 17:18 ` Jan Kratochvil
2008-08-04 19:36 ` Luis Machado
2008-08-05 13:26 ` [patch] Finish removing <bug-gdb@prep.ai.mit.edu> (PR gdb/1543) Jan Kratochvil
2008-08-06 12:13 ` Daniel Jacobowitz
2008-08-04 19:40 ` [patch] Re: Accessing tls variables across files causes a bug Ulrich Weigand
2008-08-05 8:39 ` Vinay Sridhar
2008-08-05 12:22 ` Daniel Jacobowitz
2008-08-06 11:16 ` Vinay Sridhar
2008-08-06 11:25 ` Daniel Jacobowitz [this message]
2008-08-06 11:43 ` Jan Kratochvil
2008-08-06 15:20 ` Jan Kratochvil
2008-08-27 4:37 ` Vinay Sridhar
2009-06-12 17:06 ` [resolved] " Jan Kratochvil
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=20080806112432.GA29991@caradoc.them.org \
--to=drow@false.org \
--cc=gdb-patches@sources.redhat.com \
--cc=jan.kratochvil@redhat.com \
--cc=luisgpm@linux.vnet.ibm.com \
--cc=uweigand@de.ibm.com \
--cc=vinay@linux.vnet.ibm.com \
/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