public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "anlauf at gmx dot de" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug libgomp/28456] [gomp] Segmentation fault with statically linked binaries
Date: Sat, 22 Jul 2006 12:55:00 -0000 [thread overview]
Message-ID: <20060722125548.16856.qmail@sourceware.org> (raw)
In-Reply-To: <bug-28456-6318@http.gcc.gnu.org/bugzilla/>
------- Comment #2 from anlauf at gmx dot de 2006-07-22 12:55 -------
(In reply to comment #1)
> I think this is a bug in your glibc version where static linking glibc causes
> TLS to be broken.
Andrew,
how can I find out whether this happens, and why should it happen
with static linking only? Is there a workaround for static linking?
The distributions' glibc versions, whether static or dynamic, are
supposedly the same.
For the glibc on the system mentioned above, the dynamic version claims:
% /lib/libc.so.6
GNU C Library stable release version 2.3.5 (20050802), by Roland McGrath et al.
Copyright (C) 2005 Free Software Foundation, Inc.
This is free software; see the source for copying conditions.
There is NO warranty; not even for MERCHANTABILITY or FITNESS FOR A
PARTICULAR PURPOSE.
Configured for i686-suse-linux.
Compiled by GNU CC version 4.0.2 20050901 (prerelease) (SUSE Linux).
Compiled on a Linux 2.6.12 system on 2005-09-09.
Available extensions:
GNU libio by Per Bothner
crypt add-on version 2.1 by Michael Glad and others
linuxthreads-0.10 by Xavier Leroy
GNU Libidn by Simon Josefsson
NoVersion patch for broken glibc 2.0 binaries
BIND-8.2.3-T5B
libthread_db work sponsored by Alpha Processor Inc
NIS(YP)/NIS+ NSS modules 0.19 by Thorsten Kukuk
Thread-local storage support included.
For bug reporting instructions, please see:
<http://www.gnu.org/software/libc/bugs.html>.
Cheers,
-ha
--
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=28456
next prev parent reply other threads:[~2006-07-22 12:55 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-07-21 22:24 [Bug libgomp/28456] New: " anlauf at gmx dot de
2006-07-21 22:50 ` [Bug libgomp/28456] " pinskia at gcc dot gnu dot org
2006-07-22 12:55 ` anlauf at gmx dot de [this message]
2006-07-22 22:28 ` pinskia at gcc dot gnu dot org
2006-07-23 21:06 ` anlauf at gmx dot de
2006-07-23 23:56 ` pinskia at gcc dot gnu dot org
2006-07-24 8:06 ` anlauf at gmx dot de
2006-07-24 8:09 ` pinskia at gcc dot gnu dot org
2006-07-24 8:13 ` anlauf at gmx dot de
2006-07-26 0:31 ` pinskia at gcc dot gnu dot org
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=20060722125548.16856.qmail@sourceware.org \
--to=gcc-bugzilla@gcc.gnu.org \
--cc=gcc-bugs@gcc.gnu.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).