From: "Stephen P. Becker" <geoman@gentoo.org>
To: Daniel Jacobowitz <dan@debian.org>
Cc: Ralf Baechle <ralf@linux-mips.org>,
Bryan Althouse <bryan.althouse@3phoenix.com>,
"'Linux/MIPS Development'" <linux-mips@linux-mips.org>
Subject: Re: Seg fault when compiled with -mabi=64 and -lpthread
Date: Thu, 30 Jun 2005 18:09:09 -0400 [thread overview]
Message-ID: <42C46D85.9050104@gentoo.org> (raw)
In-Reply-To: <20050630210357.GA23456@nevyn.them.org>
> Bryan seems to be using the original Red Hat gnupro 64-bit toolchain.
> I don't know how well that works nowadays; but current CVS versions do
> work, or did when I last tested (a month or two ago).
>
Hmm, well with respect to my problem, I'm using a pretty recent
toolchain, with gcc 3.4.4, binutils-2.16.1, glibc-2.3.5, and headers
from a linux-mips 2.6.11 snapshot. Interestingly, I tried to reproduce
Bryan's segfault, but could not. That code ran without error when I
linked with libpthread. Any thoughts?
-Steve
next prev parent reply other threads:[~2005-06-30 22:11 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-06-30 17:33 Seg fault when compiled with -mabi=64 and -lpthread Bryan Althouse
2005-06-30 19:08 ` Stephen P. Becker
2005-06-30 19:31 ` Bryan Althouse
2005-06-30 20:21 ` Ralf Baechle
2005-06-30 21:03 ` Daniel Jacobowitz
2005-06-30 22:09 ` Stephen P. Becker [this message]
2005-07-01 3:51 ` Daniel Jacobowitz
2005-07-01 4:44 ` Kumba
2005-07-01 8:49 ` Maciej W. Rozycki
2005-07-01 13:39 ` Daniel Jacobowitz
2005-07-01 14:10 ` Maciej W. Rozycki
2005-07-01 14:46 ` Daniel Jacobowitz
2005-07-01 15:04 ` Maciej W. Rozycki
2005-07-01 14:56 ` Stephen P. Becker
2005-07-01 15:22 ` Maciej W. Rozycki
2005-07-01 16:39 ` Stephen P. Becker
2005-07-01 17:02 ` Daniel Jacobowitz
2005-07-01 17:15 ` Stephen P. Becker
2005-07-01 15:09 ` Bryan Althouse
2005-07-01 14:54 ` sjhill
2005-07-01 15:09 ` Bryan Althouse
2005-07-01 15:29 ` Maciej W. Rozycki
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=42C46D85.9050104@gentoo.org \
--to=geoman@gentoo.org \
--cc=bryan.althouse@3phoenix.com \
--cc=dan@debian.org \
--cc=linux-mips@linux-mips.org \
--cc=ralf@linux-mips.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