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: Sun, 23 Jul 2006 21:06:00 -0000 [thread overview]
Message-ID: <20060723210609.4913.qmail@sourceware.org> (raw)
In-Reply-To: <bug-28456-6318@http.gcc.gnu.org/bugzilla/>
------- Comment #4 from anlauf at gmx dot de 2006-07-23 21:06 -------
(In reply to comment #3)
> Because less people test glibc staticly. Anyways this is a glibc bug which has
> since been fixed and it is the same problem as mentioned in PR 28351 so closing
> as a dup of that bug.
Negative. I cannot reproduce the bug PR 28351 on the machines I have
access to which are i386 (32 bit). I don't believe it is the same bug.
--
anlauf at gmx dot de changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|RESOLVED |UNCONFIRMED
Resolution|DUPLICATE |
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=28456
next prev parent reply other threads:[~2006-07-23 21:06 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
2006-07-22 22:28 ` pinskia at gcc dot gnu dot org
2006-07-23 21:06 ` anlauf at gmx dot de [this message]
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=20060723210609.4913.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).