From: Jan Kratochvil <jan.kratochvil@redhat.com>
To: gdb-patches@sources.redhat.com
Cc: Vinay Sridhar <vinay@linux.vnet.ibm.com>,
Daniel Jacobowitz <drow@false.org>,
luisgpm@linux.vnet.ibm.com, uweigand@de.ibm.com,
Tom Tromey <tromey@redhat.com>
Subject: [resolved] Re: [patch] Re: Accessing tls variables across files causes a bug
Date: Fri, 12 Jun 2009 17:06:00 -0000 [thread overview]
Message-ID: <20090612170553.GA6907@host0.dyn.jankratochvil.net> (raw)
In-Reply-To: <20080806151933.GA32530@host0.dyn.jankratochvil.net>
Hi,
just marking this mail thread as resolved by later mail threads:
The TLS TLS cross-file references fix got checked-in by:
Re: [patch] Accessing tls variables across files causes a bug
http://sourceware.org/ml/gdb-patches/2008-12/msg00016.html
http://sourceware.org/ml/gdb-cvs/2008-12/msg00009.html
Why LOC_UNRESOLVED existence makes sense for GDB (testcase on it):
Re: [patch] Fix C `extern' shadowing in a local block
http://sourceware.org/ml/gdb-patches/2009-04/msg00051.html
http://sourceware.org/ml/gdb-cvs/2009-04/msg00021.html
Thanks,
Jan
On Wed, 06 Aug 2008 17:19:33 +0200, Jan Kratochvil wrote:
> On Wed, 06 Aug 2008 13:42:41 +0200, Jan Kratochvil wrote:
> > Another possibility is that LOC_UNRESOLVED may no longer be needed for recent
> > gcc debuginfos always(?) containting `DW_AT_location's, therefore we would not
> > have to deal with `minimal_symbol's in this case at all.
>
> Attached.
>
> It has no regressions on x86_64, Fedora gcc-4.3.1-6.x86_64 (but gcc-4.3 has
> GDB regressions against gcc-4.1). Also tried there are no regressions by
> check//unix/-gstabs+ (although the three new TLS testcases FAIL there).
>
> I do not fully grok why psymtabs were created for DW_AT_type DIEs with no
> DW_AT_location. IMO (DW_AT_location || DW_AT_const_value) is the right
> condition (DW_AT_const_value requirement was found by a testsuite run).
>
>
> Regards,
> Jan
> 2008-08-06 Jan Kratochvil <jan.kratochvil@redhat.com>
>
> Fix resolving external references to TLS variables.
> * ada-lang.c (ada_add_block_symbols): Remove LOC_UNRESOLVED.
> * ax-gdb.c (gen_var_ref): Likewise.
> * gen_var_ref (symbol_read_needs_frame, read_var_value): Likewise.
> * m2-exp.y (yylex): Likewise.
> * printcmd.c (address_info): Likewise.
> * symmisc.c (print_symbol, print_partial_symbols): Likewise.
> * symtab.h (enum address_class): Likewise.
> * tracepoint.c (collect_symbol, scope_info): Likewise.
> * mi/mi-cmd-stack.c (list_args_or_locals): Likewise.
> * stabsread.c (scan_file_globals): Complain even on LOC_STATIC symbols.
> Set such symbols to LOC_UNDEF instead of LOC_UNRESOLVED.
> * dwarf2read.c (struct partial_die_info): Remove the field HAS_TYPE.
> New field HAS_CONST_VALUE.
> (add_partial_symbol) <DW_TAG_variable>: HAS_TYPE condition removed.
> HAS_CONST_VALUE condition added. Comment updated.
> (read_partial_die) <DW_AT_type>: Case removed.
> (read_partial_die) <DW_AT_const_value>: New case.
> (new_symbol): Remove setting LOC_UNRESOLVED. Comment updated.
>
> 2008-08-06 Jan Kratochvil <jan.kratochvil@redhat.com>
>
> Update for removed LOC_UNRESOLVED, test resolving external references
> to TLS variables.
> * gdb.dwarf2/dw2-noloc.S: New variable "optloc".
> * gdb.dwarf2/dw2-noloc.exp: Test the new variable "optloc". Update the
> current message for the variable "noloc".
> * gdb.threads/tls.exp: New tests to print A_THREAD_LOCAL and
> FILE2_THREAD_LOCAL.
> (testfile2, srcfile2): New variables.
> * gdb.threads/tls.c (file2_thread_local)
> (function_referencing_file2_thread_local): New.
> * gdb.threads/tls2.c: New file.
prev parent reply other threads:[~2009-06-12 17:06 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
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 ` Jan Kratochvil [this message]
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=20090612170553.GA6907@host0.dyn.jankratochvil.net \
--to=jan.kratochvil@redhat.com \
--cc=drow@false.org \
--cc=gdb-patches@sources.redhat.com \
--cc=luisgpm@linux.vnet.ibm.com \
--cc=tromey@redhat.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