public inbox for gdb-prs@sourceware.org
help / color / mirror / Atom feed
From: "jan.kratochvil at redhat dot com" <sourceware-bugzilla@sourceware.org>
To: gdb-prs@sourceware.org
Subject: [Bug threads/16954] New: Improve TLS variables glibc compatibility
Date: Fri, 16 May 2014 19:20:00 -0000 [thread overview]
Message-ID: <bug-16954-4717@http.sourceware.org/bugzilla/> (raw)
https://sourceware.org/bugzilla/show_bug.cgi?id=16954
Bug ID: 16954
Summary: Improve TLS variables glibc compatibility
Product: gdb
Version: HEAD
Status: NEW
Severity: normal
Priority: P2
Component: threads
Assignee: unassigned at sourceware dot org
Reporter: jan.kratochvil at redhat dot com
Target: *-linux-gnu
With post-2.19.90 glibcs the GDB patch posted below still works but it is
needlessly incorrect - it depends on assumption glibc assigns module id 1 to
static executables.
GDB fix post for compatibility with pre-2.19.90 glibcs:
[patch] Fix TLS access for -static -pthread
https://sourceware.org/ml/gdb-patches/2014-04/msg00155.html
glibc fix in glibc-2.19.90: PR libc/16831
https://sourceware.org/git/gitweb.cgi?p=glibc.git;a=commitdiff;h=f737dfd071f12584316ef90f2c71e33c2dc9801e
Original post (IMO obsolete now):
TLS variables access for -static -lpthread executables
https://sourceware.org/ml/libc-help/2014-03/msg00024.html
--
You are receiving this mail because:
You are on the CC list for the bug.
next reply other threads:[~2014-05-16 19:20 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-05-16 19:20 jan.kratochvil at redhat dot com [this message]
2014-05-16 19:22 ` [Bug threads/16954] " jan.kratochvil at redhat dot com
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=bug-16954-4717@http.sourceware.org/bugzilla/ \
--to=sourceware-bugzilla@sourceware.org \
--cc=gdb-prs@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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).