Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Jan Kratochvil <jan.kratochvil@redhat.com>
To: Tom Tromey <tromey@redhat.com>
Cc: gdb-patches@sourceware.org
Subject: [commit] [patch] Fix TLS access for -static -pthread
Date: Wed, 21 May 2014 14:28:00 -0000	[thread overview]
Message-ID: <20140521142832.GA19494@host2.jankratochvil.net> (raw)
In-Reply-To: <8761kzp6by.fsf@fleche.redhat.com>

On Wed, 21 May 2014 16:14:09 +0200, Tom Tromey wrote:
> Jan> I have put there:
> Jan> +      /* This code path handles the case of -static -pthread executables:
> Jan> +	 https://sourceware.org/ml/libc-help/2014-03/msg00024.html
> Jan> +	 For older GNU libc r_debug.r_map is NULL.  For GNU libc after
> Jan> +	 PR libc/16831 due to GDB PR threads/16954 LOAD_MODULE is also NULL.
> Jan> +	 The constant number 1 depends on GNU __libc_setup_tls
> Jan> +	 initialization of l_tls_modid to 1.  */
> 
> Thanks, that looks good.

Checked in:
	5876f5032f60c45c4bd19e7ea7d0c14d0346b93e


Jan


  reply	other threads:[~2014-05-21 14:28 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-04-10 11:52 Jan Kratochvil
2014-04-11 11:03 ` Jan Kratochvil
2014-05-20 15:10   ` Tom Tromey
2014-05-20 15:18     ` Jan Kratochvil
2014-05-20 15:10 ` Tom Tromey
2014-05-21 12:17   ` Jan Kratochvil
2014-05-21 14:14     ` Tom Tromey
2014-05-21 14:28       ` Jan Kratochvil [this message]
2014-06-05  7:17 ` Yao Qi
2014-06-05  8:06   ` Jan Kratochvil
2014-06-05  9:32     ` Yao Qi
2014-06-05  9:39       ` Jan Kratochvil
2014-06-05 14:20         ` Yao Qi
2014-06-05 15:23           ` Pedro Alves
2014-06-06  2:26             ` Yao Qi
2014-06-05 15:18     ` Pedro Alves
2014-06-06 15:03       ` Jan Kratochvil
2014-06-06  2:36     ` Yao Qi
2014-06-06  6:16       ` Yao Qi
2014-06-06 14:20         ` Jan Kratochvil
2014-06-06  5:34     ` Sergio Durigan Junior
2014-06-06 14:21       ` 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=20140521142832.GA19494@host2.jankratochvil.net \
    --to=jan.kratochvil@redhat.com \
    --cc=gdb-patches@sourceware.org \
    --cc=tromey@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