public inbox for gdb-prs@sourceware.org
help / color / mirror / Atom feed
From: "jan dot kratochvil at redhat dot com" <sourceware-bugzilla@sourceware.org>
To: gdb-prs@sourceware.org
Subject: [Bug threads/11795] New: Support __thread variables without libpthread
Date: Wed, 07 Jul 2010 17:36:00 -0000	[thread overview]
Message-ID: <20100707173634.11795.jan.kratochvil@redhat.com> (raw)

echo 'main(){}'|gcc -g -x c -;./gdb -nx -ex start -ex 'p errno' ./a.out 
Cannot find thread-local variables on this target

It happens for any variable marked by __thread when -lpthread is not used.
Fedora GDB has some hacks such as using `*__errno_location()' instead of `errno'.

The proper way would be glibc extension to support __thread variables even
without -lpthread mode as they are used not just for `errno'.
Draft patches included.

-- 
           Summary: Support __thread variables without libpthread
           Product: gdb
           Version: unknown
            Status: UNCONFIRMED
          Severity: enhancement
          Priority: P2
         Component: threads
        AssignedTo: unassigned at sourceware dot org
        ReportedBy: jan dot kratochvil at redhat dot com
                CC: gdb-prs at sourceware dot org


http://sourceware.org/bugzilla/show_bug.cgi?id=11795

------- You are receiving this mail because: -------
You are on the CC list for the bug, or are watching someone who is.


             reply	other threads:[~2010-07-07 17:36 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-07-07 17:36 jan dot kratochvil at redhat dot com [this message]
2010-07-07 17:37 ` [Bug threads/11795] " jan dot kratochvil at redhat dot com
2010-07-07 17:38 ` jan dot 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=20100707173634.11795.jan.kratochvil@redhat.com \
    --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).