From: Mark Wielaard <mjw@redhat.com>
To: Jan Kratochvil <jan.kratochvil@redhat.com>
Cc: gdb-patches@sourceware.org
Subject: Re: [patch+7.12.1 2/2] Fix TLS (such as 'errno') regression
Date: Mon, 10 Oct 2016 10:45:00 -0000 [thread overview]
Message-ID: <1476096311.21750.142.camel@redhat.com> (raw)
In-Reply-To: <20161009185647.GB13645@host1.jankratochvil.net>
On Sun, 2016-10-09 at 20:56 +0200, Jan Kratochvil wrote:
> 2273f0ac95a79ce29ef42025c63f90e82cf907d7 is the first bad commit
> commit 2273f0ac95a79ce29ef42025c63f90e82cf907d7
> Author: Tom Tromey <tromey@redhat.com>
> Date: Tue Oct 15 13:28:57 2013 -0600
> change minsyms not to be relocated at read-time
> [FYI v3 06/10] change minsyms not to be relocated at read-time
> Message-Id: <1393441273-32268-7-git-send-email-tromey@redhat.com>
> https://sourceware.org/ml/gdb-patches/2014-02/msg00798.html
>
> mv /usr/lib/debug /usr/lib/debug-x
> echo 'int main(){}'|gcc -pthread -x c -
> ./gdb -q -ex start -ex 'set debug expr 1' -ex 'p errno' ./a.out
> 0 UNOP_MEMVAL_TLS TLS type @0x35df7e0 (__thread /* "/lib64/libc.so.6" */ <thread local variable, no debug info>)
> 4 OP_LONG Type @0x35df850 (__CORE_ADDR), value 140737345728528 (0x7ffff77fb010)
> Cannot access memory at address 0xffffef7c9698
> ->
> 0 UNOP_MEMVAL_TLS TLS type @0x3ad9520 (__thread /* "/lib64/libc.so.6" */ <thread local variable, no debug info>)
> 4 OP_LONG Type @0x3ad9590 (__CORE_ADDR), value 16 (0x10)
> $1 = 0
>
> With glibc debuginfo, that is without: mv /usr/lib/debug /usr/lib/debug-x
> 0 OP_VAR_VALUE Block @0x3b30e70, symbol @0x3b30d10 (errno)
> $1 = 0
> So such case is unrelated to this patch and the regression is not visible with
> glibc debuginfo installed.
FYI. This issue, cause and fix look very similar to PR varobj/18564
"regression in showing __thread so extern variable".
Might there be other places that need similar adjustments for getting at
the values of tls variables?
next prev parent reply other threads:[~2016-10-10 10:45 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-10-09 18:57 Jan Kratochvil
2016-10-10 10:45 ` Mark Wielaard [this message]
2016-10-10 14:50 ` Tom Tromey
2016-10-10 15:13 ` Jan Kratochvil
2016-10-10 22:43 ` Tom Tromey
2017-09-06 11:58 ` Pedro Alves
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=1476096311.21750.142.camel@redhat.com \
--to=mjw@redhat.com \
--cc=gdb-patches@sourceware.org \
--cc=jan.kratochvil@redhat.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