From: Sergio Durigan Junior <sergiodj@redhat.com>
To: Jan Kratochvil <jan.kratochvil@redhat.com>
Cc: Yao Qi <yao@codesourcery.com>, gdb-patches@sourceware.org
Subject: Re: [patch] Fix TLS access for -static -pthread
Date: Fri, 06 Jun 2014 05:34:00 -0000 [thread overview]
Message-ID: <m3egz2d2jq.fsf@redhat.com> (raw)
In-Reply-To: <20140605080639.GA32146@host2.jankratochvil.net> (Jan Kratochvil's message of "Thu, 5 Jun 2014 10:06:39 +0200")
On Thursday, June 05 2014, Jan Kratochvil wrote:
>> Is it good to you? b.t.w, this case is UNSUPPORTED on FC 20, because
>> staticthreads.c can't be compiled. I guess this case requires
>> some recent version of glibc.
>
> I do not see any unsupported case on
> * Fedora 20 x86_64 updates-testing disabled with debuginfos
> * Fedora 20 x86_64 updates-testing enabled with debuginfos
> * Fedora 20 x86_64 updates-testing enabled without debuginfos
> * Fedora Rawhide x86_64 with debuginfos
> for both nat and gdbserver runs.
>
> Sergio said he saw some problem with mktemp symbol on some Fedora but I do not
> have that reproducible so I cannot fix it.
I saw this:
Executing on host: gcc ../../../gdb/testsuite/gdb.threads/staticthreads.c -static -DHAVE_TLS -g -lpthread -lm -o /patch/to/gdb/testsuite/gdb.threads/staticthreads (timeout = 300)
spawn -ignore SIGHUP gcc ../../../gdb/testsuite/gdb.threads/staticthreads.c -static -DHAVE_TLS -g -lpthread -lm -o /patch/to/gdb/testsuite/gdb.threads/staticthreads^M
/usr/lib/gcc/x86_64-redhat-linux/4.4.7/../../../../lib64/libpthread.a(libpthread.o): In function `sem_open':^M
(.text+0x774d): warning: the use of `mktemp' is dangerous, better use `mkstemp'^M
output is:
/usr/lib/gcc/x86_64-redhat-linux/4.4.7/../../../../lib64/libpthread.a(libpthread.o): In function `sem_open':^M
(.text+0x774d): warning: the use of `mktemp' is dangerous, better use `mkstemp'^M
This is on RHEL-6.5, with gcc (GCC) 4.4.7 20120313 (Red Hat 4.4.7-4).
I had to do a small workaround in gdb_compile_pthreads (from
testsuite/lib/gdb.exp) in order to make the compilation succeed.
--
Sergio
GPG key ID: 65FC5E36
Please send encrypted e-mail if possible
http://blog.sergiodj.net/
next prev parent reply other threads:[~2014-06-06 5:34 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 ` [commit] " Jan Kratochvil
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 [this message]
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=m3egz2d2jq.fsf@redhat.com \
--to=sergiodj@redhat.com \
--cc=gdb-patches@sourceware.org \
--cc=jan.kratochvil@redhat.com \
--cc=yao@codesourcery.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).