From: Ralf Baechle <ralf@linux-mips.org>
To: Bryan Althouse <bryan.althouse@3phoenix.com>
Cc: "'Linux/MIPS Development'" <linux-mips@linux-mips.org>
Subject: Re: Seg fault when compiled with -mabi=64 and -lpthread
Date: Thu, 30 Jun 2005 21:21:11 +0100 [thread overview]
Message-ID: <20050630202111.GC3245@linux-mips.org> (raw)
In-Reply-To: <20050630173409Z8226102-3678+735@linux-mips.org>
On Thu, Jun 30, 2005 at 01:33:39PM -0400, Bryan Althouse wrote:
> The executable will seg fault. If I remove the -lpthread, it is fine.
> Also, if I change the 64 to 32, it is fine.
I fear you may be hitting these problems simple because you're the first
through the mine field of 64-bit pthreads ;-) So far most people are
simple running 32-bit software on their 64-bit kernels. No reason to
panic though, most of the bits are in place, it's just the one or other
insect hiding in the code.
Ralf
next prev parent reply other threads:[~2005-06-30 20:22 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 [this message]
2005-06-30 21:03 ` Daniel Jacobowitz
2005-06-30 22:09 ` Stephen P. Becker
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=20050630202111.GC3245@linux-mips.org \
--to=ralf@linux-mips.org \
--cc=bryan.althouse@3phoenix.com \
--cc=linux-mips@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