From mboxrd@z Thu Jan 1 00:00:00 1970 Received: with ECARTIS (v1.0.0; list linux-mips); Thu, 30 Jun 2005 18:34:31 +0100 (BST) Received: from sccrmhc12.comcast.net ([IPv6:::ffff:204.127.202.56]:50175 "EHLO sccrmhc12.comcast.net") by linux-mips.org with ESMTP id ; Thu, 30 Jun 2005 18:34:09 +0100 Received: from ba3pi (pcp0010731669pcs.howard01.md.comcast.net[69.243.71.130]) by comcast.net (sccrmhc12) with SMTP id <2005063017334001200h9fsne>; Thu, 30 Jun 2005 17:33:45 +0000 From: "Bryan Althouse" To: "'Linux/MIPS Development'" Subject: Seg fault when compiled with -mabi=64 and -lpthread Date: Thu, 30 Jun 2005 13:33:39 -0400 MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="----=_NextPart_000_0057_01C57D78.566479A0" X-Mailer: Microsoft Office Outlook, Build 11.0.6353 X-MIMEOLE: Produced By Microsoft MimeOLE V6.00.2900.2180 Thread-index: AcV9mdoBnM33Jz9ERSG+iD9SiRy2CQ== Message-Id: <20050630173409Z8226102-3678+735@linux-mips.org> Return-Path: X-Envelope-To: <"|/home/ecartis/ecartis -s linux-mips"> (uid 0) X-Orcpt: rfc822;linux-mips@linux-mips.org Original-Recipient: rfc822;linux-mips@linux-mips.org X-archive-position: 8268 X-ecartis-version: Ecartis v1.0.0 Sender: linux-mips-bounce@linux-mips.org Errors-to: linux-mips-bounce@linux-mips.org X-original-sender: bryan.althouse@3phoenix.com Precedence: bulk X-list: linux-mips This is a multi-part message in MIME format. ------=_NextPart_000_0057_01C57D78.566479A0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit I have a problem when linking a 64 bit application with libpthread. I appears to link fine, but it will seg fault when I execute it. I wrote an empty C program called empty.c: int main (void) { return 0; } I cross compile it with: /opt/redhat/mips64linux-031001/H-i686-pc-linux-gnulibc2.2/bin/mips64-linux-g nu-gcc -mabi=64 empty.c -o empty -lpthread The executable will seg fault. If I remove the -lpthread, it is fine. Also, if I change the 64 to 32, it is fine. Maybe I have a bad libpthread in /lib64? If I type "file /lib64/libpthread-0.10.so" I get: "ELF 64-bit MSB shared object, mips-3 MIPS R3000_BE, version 1, not stripped". Looks fine to me. Should I cross compile and replace libpthread? If so, where can I find the source? The other strange thing is that ldd does not work on 64 bit applications. It will always return: "not a dynamic executable". Does anyone know how this could be fixed? I'm using a PMC Yosemite board with an RM9224 processor. The kernel is 2.6.12 64bit SMP. I am using the PMC supplied cross compile tools, kernel, and NFS file system. Thanks for your help! Bryan ------=_NextPart_000_0057_01C57D78.566479A0 Content-Type: text/html; charset="us-ascii" Content-Transfer-Encoding: quoted-printable

I have a problem when linking a 64 bit application = with libpthread.  I appears to link fine, but it will seg fault when I = execute it.  I wrote an empty C program called = empty.c:

 

int main (void)

{ 

    return = 0;

}

 

I cross compile it with:

/opt/redhat/mips64linux-031001/H-i686-pc-linux-gnulibc= 2.2/bin/mips64-linux-gnu-gcc –mabi=3D64 empty.c –o empty = –lpthread

The executable will seg fault.  If I remove the –lpthread, it is fine.  Also, if I change the 64 to 32, it is = fine.

 

Maybe I have a bad libpthread in /lib64?  If I = type “file /lib64/libpthread-0.10.so” I get: “ELF 64-bit MSB shared = object, mips-3 MIPS R3000_BE, version 1, not stripped”.  Looks fine = to me.  Should I cross compile and replace libpthread?  If so, = where can I find the source?

 

The other strange thing is that ldd does not work on = 64 bit applications.  It will always return:  “not a dynamic executable”.  Does anyone know how this could be fixed?  =

 

I’m using a PMC Yosemite board with an RM9224 processor.  The kernel is 2.6.12 64bit SMP.  I am using the = PMC supplied cross compile tools, kernel, and NFS file system. =

 

Thanks for your help!

Bryan

 

 

------=_NextPart_000_0057_01C57D78.566479A0-- From mboxrd@z Thu Jan 1 00:00:00 1970 Received: with ECARTIS (v1.0.0; list linux-mips); Thu, 30 Jun 2005 20:10:14 +0100 (BST) Received: from lennier.cc.vt.edu ([IPv6:::ffff:198.82.162.213]:49354 "EHLO lennier.cc.vt.edu") by linux-mips.org with ESMTP id ; Thu, 30 Jun 2005 20:09:56 +0100 Received: from dagger.cc.vt.edu (IDENT:mirapoint@[10.1.1.11]) by lennier.cc.vt.edu (8.12.11/8.12.11) with ESMTP id j5UJ8qS5023139; Thu, 30 Jun 2005 15:09:02 -0400 Received: from [128.173.184.73] (gs4073.geos.vt.edu [128.173.184.73]) by dagger.cc.vt.edu (MOS 3.6.4-CR) with ESMTP id DOQ23270; Thu, 30 Jun 2005 15:08:45 -0400 (EDT) Message-ID: <42C44336.1080401@gentoo.org> Date: Thu, 30 Jun 2005 15:08:38 -0400 From: "Stephen P. Becker" User-Agent: Mozilla Thunderbird 1.0.2 (X11/20050624) X-Accept-Language: en-us, en MIME-Version: 1.0 To: Bryan Althouse CC: "'Linux/MIPS Development'" Subject: Re: Seg fault when compiled with -mabi=64 and -lpthread References: <20050630173409Z8226102-3678+735@linux-mips.org> In-Reply-To: <20050630173409Z8226102-3678+735@linux-mips.org> Content-Type: text/plain; charset=windows-1252 Content-Transfer-Encoding: 8bit Return-Path: X-Envelope-To: <"|/home/ecartis/ecartis -s linux-mips"> (uid 0) X-Orcpt: rfc822;linux-mips@linux-mips.org Original-Recipient: rfc822;linux-mips@linux-mips.org X-archive-position: 8272 X-ecartis-version: Ecartis v1.0.0 Sender: linux-mips-bounce@linux-mips.org Errors-to: linux-mips-bounce@linux-mips.org X-original-sender: geoman@gentoo.org Precedence: bulk X-list: linux-mips Bryan Althouse wrote: > I have a problem when linking a 64 bit application with libpthread. I > appears to link fine, but it will seg fault when I execute it. I wrote > an empty C program called empty.c: > > > > int main (void) > > { > > return 0; > > } > > > > I cross compile it with: > > /opt/redhat/mips64linux-031001/H-i686-pc-linux-gnulibc2.2/bin/mips64-linux-gnu-gcc > –mabi=64 empty.c –o empty –lpthread > > The executable will seg fault. If I remove the –lpthread, it is fine. > Also, if I change the 64 to 32, it is fine. > > > > Maybe I have a bad libpthread in /lib64? If I type “file > /lib64/libpthread-0.10.so” I get: “ELF 64-bit MSB shared object, mips-3 > MIPS R3000_BE, version 1, not stripped”. Looks fine to me. Should I > cross compile and replace libpthread? If so, where can I find the source? > Wow, so I'm not just smoking crack. I ran into essentially the same exact problem with my n32 userland while trying to build glib (not glibc). The configure script kept dying while trying to determine if libpthread was available. Looking at the config.log, I noticed that the conftest code was causing a segfault. Furthermore, this causes a kernel oops (you should check your kernel logs for an oops). I isolated the conftest code, and it is available at: http://beerandrocks.net:8080/~spbecker/oops/ In that directory is also a statically linked big endian n32 executable, as well as dumps of oops messages that I was able to reproduce 100% of the time on both ip32 and ip22 systems. If anyone is in an experimenting mood, try to run that executable on a mips64 box (with n32 binary support enabled obviously) and see what happens. The interesting thing about this problem is that it only happens with recent kernels. I can't speak for 2.6.11 since I haven't tested it yet, but the oops only occurred while running 2.6.12 from cvs HEAD. When running my 2.6.10 build that has been on my indy for some time, the conftest code runs fine without any segfault, and there is no kernel oops. -Steve From mboxrd@z Thu Jan 1 00:00:00 1970 Received: with ECARTIS (v1.0.0; list linux-mips); Thu, 30 Jun 2005 20:32:14 +0100 (BST) Received: from sccrmhc12.comcast.net ([IPv6:::ffff:204.127.202.56]:3821 "EHLO sccrmhc12.comcast.net") by linux-mips.org with ESMTP id ; Thu, 30 Jun 2005 20:31:55 +0100 Received: from ba3pi (pcp0010731669pcs.howard01.md.comcast.net[69.243.71.130]) by comcast.net (sccrmhc12) with SMTP id <2005063019313601200h96rie>; Thu, 30 Jun 2005 19:31:37 +0000 From: "Bryan Althouse" To: "'Stephen P. Becker'" Cc: "'Linux/MIPS Development'" Subject: RE: Seg fault when compiled with -mabi=64 and -lpthread Date: Thu, 30 Jun 2005 15:31:36 -0400 MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit X-Mailer: Microsoft Office Outlook, Build 11.0.6353 X-MIMEOLE: Produced By Microsoft MimeOLE V6.00.2900.2180 Thread-index: AcV9pz+aRx+9hWzVTzilb9rL9PauPgAAlkvQ In-Reply-To: <42C44336.1080401@gentoo.org> Message-Id: <20050630193155Z8226101-3678+745@linux-mips.org> Return-Path: X-Envelope-To: <"|/home/ecartis/ecartis -s linux-mips"> (uid 0) X-Orcpt: rfc822;linux-mips@linux-mips.org Original-Recipient: rfc822;linux-mips@linux-mips.org X-archive-position: 8274 X-ecartis-version: Ecartis v1.0.0 Sender: linux-mips-bounce@linux-mips.org Errors-to: linux-mips-bounce@linux-mips.org X-original-sender: bryan.althouse@3phoenix.com Precedence: bulk X-list: linux-mips Steve, I don't see a kernel oops. I checked /var/log/messages, and a few others. I have verified that klogd and syslogd are running. Bryan -----Original Message----- From: Stephen P. Becker [mailto:geoman@gentoo.org] Sent: Thursday, June 30, 2005 3:09 PM To: Bryan Althouse Cc: 'Linux/MIPS Development' Subject: Re: Seg fault when compiled with -mabi=64 and -lpthread Bryan Althouse wrote: > I have a problem when linking a 64 bit application with libpthread. I > appears to link fine, but it will seg fault when I execute it. I wrote > an empty C program called empty.c: > > > > int main (void) > > { > > return 0; > > } > > > > I cross compile it with: > > /opt/redhat/mips64linux-031001/H-i686-pc-linux-gnulibc2.2/bin/mips64-linux-g nu-gcc > -mabi=64 empty.c -o empty -lpthread > > The executable will seg fault. If I remove the -lpthread, it is fine. > Also, if I change the 64 to 32, it is fine. > > > > Maybe I have a bad libpthread in /lib64? If I type "file > /lib64/libpthread-0.10.so" I get: "ELF 64-bit MSB shared object, mips-3 > MIPS R3000_BE, version 1, not stripped". Looks fine to me. Should I > cross compile and replace libpthread? If so, where can I find the source? > Wow, so I'm not just smoking crack. I ran into essentially the same exact problem with my n32 userland while trying to build glib (not glibc). The configure script kept dying while trying to determine if libpthread was available. Looking at the config.log, I noticed that the conftest code was causing a segfault. Furthermore, this causes a kernel oops (you should check your kernel logs for an oops). I isolated the conftest code, and it is available at: http://beerandrocks.net:8080/~spbecker/oops/ In that directory is also a statically linked big endian n32 executable, as well as dumps of oops messages that I was able to reproduce 100% of the time on both ip32 and ip22 systems. If anyone is in an experimenting mood, try to run that executable on a mips64 box (with n32 binary support enabled obviously) and see what happens. The interesting thing about this problem is that it only happens with recent kernels. I can't speak for 2.6.11 since I haven't tested it yet, but the oops only occurred while running 2.6.12 from cvs HEAD. When running my 2.6.10 build that has been on my indy for some time, the conftest code runs fine without any segfault, and there is no kernel oops. -Steve From mboxrd@z Thu Jan 1 00:00:00 1970 Received: with ECARTIS (v1.0.0; list linux-mips); Thu, 30 Jun 2005 21:22:09 +0100 (BST) Received: from alg138.algor.co.uk ([IPv6:::ffff:62.254.210.138]:6889 "EHLO bacchus.net.dhis.org") by linux-mips.org with ESMTP id ; Thu, 30 Jun 2005 21:21:52 +0100 Received: from dea.linux-mips.net (localhost.localdomain [127.0.0.1]) by bacchus.net.dhis.org (8.13.4/8.13.1) with ESMTP id j5UKLCXA005350; Thu, 30 Jun 2005 21:21:12 +0100 Received: (from ralf@localhost) by dea.linux-mips.net (8.13.4/8.13.4/Submit) id j5UKLBGS005349; Thu, 30 Jun 2005 21:21:11 +0100 Date: Thu, 30 Jun 2005 21:21:11 +0100 From: Ralf Baechle To: Bryan Althouse Cc: "'Linux/MIPS Development'" Subject: Re: Seg fault when compiled with -mabi=64 and -lpthread Message-ID: <20050630202111.GC3245@linux-mips.org> References: <20050630173409Z8226102-3678+735@linux-mips.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20050630173409Z8226102-3678+735@linux-mips.org> User-Agent: Mutt/1.4.2.1i Return-Path: X-Envelope-To: <"|/home/ecartis/ecartis -s linux-mips"> (uid 0) X-Orcpt: rfc822;linux-mips@linux-mips.org Original-Recipient: rfc822;linux-mips@linux-mips.org X-archive-position: 8276 X-ecartis-version: Ecartis v1.0.0 Sender: linux-mips-bounce@linux-mips.org Errors-to: linux-mips-bounce@linux-mips.org X-original-sender: ralf@linux-mips.org Precedence: bulk X-list: linux-mips 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 From mboxrd@z Thu Jan 1 00:00:00 1970 Received: with ECARTIS (v1.0.0; list linux-mips); Thu, 30 Jun 2005 22:04:34 +0100 (BST) Received: from nevyn.them.org ([IPv6:::ffff:66.93.172.17]:53185 "EHLO nevyn.them.org") by linux-mips.org with ESMTP id ; Thu, 30 Jun 2005 22:04:13 +0100 Received: from drow by nevyn.them.org with local (Exim 4.51) id 1Do6CU-0006KK-9l; Thu, 30 Jun 2005 17:03:58 -0400 Date: Thu, 30 Jun 2005 17:03:58 -0400 From: Daniel Jacobowitz To: Ralf Baechle Cc: Bryan Althouse , 'Linux/MIPS Development' Subject: Re: Seg fault when compiled with -mabi=64 and -lpthread Message-ID: <20050630210357.GA23456@nevyn.them.org> References: <20050630173409Z8226102-3678+735@linux-mips.org> <20050630202111.GC3245@linux-mips.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20050630202111.GC3245@linux-mips.org> User-Agent: Mutt/1.5.8i Return-Path: X-Envelope-To: <"|/home/ecartis/ecartis -s linux-mips"> (uid 0) X-Orcpt: rfc822;linux-mips@linux-mips.org Original-Recipient: rfc822;linux-mips@linux-mips.org X-archive-position: 8278 X-ecartis-version: Ecartis v1.0.0 Sender: linux-mips-bounce@linux-mips.org Errors-to: linux-mips-bounce@linux-mips.org X-original-sender: dan@debian.org Precedence: bulk X-list: linux-mips On Thu, Jun 30, 2005 at 09:21:11PM +0100, Ralf Baechle wrote: > 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. 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). -- Daniel Jacobowitz CodeSourcery, LLC From mboxrd@z Thu Jan 1 00:00:00 1970 Received: with ECARTIS (v1.0.0; list linux-mips); Thu, 30 Jun 2005 23:11:00 +0100 (BST) Received: from lennier.cc.vt.edu ([IPv6:::ffff:198.82.162.213]:57566 "EHLO lennier.cc.vt.edu") by linux-mips.org with ESMTP id ; Thu, 30 Jun 2005 23:10:41 +0100 Received: from zidane.cc.vt.edu (IDENT:mirapoint@[10.1.1.13]) by lennier.cc.vt.edu (8.12.11/8.12.11) with ESMTP id j5UM9GNQ003605; Thu, 30 Jun 2005 18:09:26 -0400 Received: from [192.168.1.2] (68-232-96-93.chvlva.adelphia.net [68.232.96.93]) by zidane.cc.vt.edu (MOS 3.6.4-CR) with ESMTP id DMW00949 (AUTH spbecker); Thu, 30 Jun 2005 18:09:10 -0400 (EDT) Message-ID: <42C46D85.9050104@gentoo.org> Date: Thu, 30 Jun 2005 18:09:09 -0400 From: "Stephen P. Becker" User-Agent: Mozilla Thunderbird 1.0.2 (X11/20050625) X-Accept-Language: en-us, en MIME-Version: 1.0 To: Daniel Jacobowitz CC: Ralf Baechle , Bryan Althouse , "'Linux/MIPS Development'" Subject: Re: Seg fault when compiled with -mabi=64 and -lpthread References: <20050630173409Z8226102-3678+735@linux-mips.org> <20050630202111.GC3245@linux-mips.org> <20050630210357.GA23456@nevyn.them.org> In-Reply-To: <20050630210357.GA23456@nevyn.them.org> Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Return-Path: X-Envelope-To: <"|/home/ecartis/ecartis -s linux-mips"> (uid 0) X-Orcpt: rfc822;linux-mips@linux-mips.org Original-Recipient: rfc822;linux-mips@linux-mips.org X-archive-position: 8279 X-ecartis-version: Ecartis v1.0.0 Sender: linux-mips-bounce@linux-mips.org Errors-to: linux-mips-bounce@linux-mips.org X-original-sender: geoman@gentoo.org Precedence: bulk X-list: linux-mips > 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 From mboxrd@z Thu Jan 1 00:00:00 1970 Received: with ECARTIS (v1.0.0; list linux-mips); Fri, 01 Jul 2005 04:51:39 +0100 (BST) Received: from nevyn.them.org ([IPv6:::ffff:66.93.172.17]:31150 "EHLO nevyn.them.org") by linux-mips.org with ESMTP id ; Fri, 1 Jul 2005 04:51:21 +0100 Received: from drow by nevyn.them.org with local (Exim 4.51) id 1DoCYT-0002VU-L9; Thu, 30 Jun 2005 23:51:05 -0400 Date: Thu, 30 Jun 2005 23:51:05 -0400 From: Daniel Jacobowitz To: "Stephen P. Becker" Cc: Ralf Baechle , Bryan Althouse , 'Linux/MIPS Development' Subject: Re: Seg fault when compiled with -mabi=64 and -lpthread Message-ID: <20050701035105.GA9601@nevyn.them.org> References: <20050630173409Z8226102-3678+735@linux-mips.org> <20050630202111.GC3245@linux-mips.org> <20050630210357.GA23456@nevyn.them.org> <42C46D85.9050104@gentoo.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <42C46D85.9050104@gentoo.org> User-Agent: Mutt/1.5.8i Return-Path: X-Envelope-To: <"|/home/ecartis/ecartis -s linux-mips"> (uid 0) X-Orcpt: rfc822;linux-mips@linux-mips.org Original-Recipient: rfc822;linux-mips@linux-mips.org X-archive-position: 8283 X-ecartis-version: Ecartis v1.0.0 Sender: linux-mips-bounce@linux-mips.org Errors-to: linux-mips-bounce@linux-mips.org X-original-sender: dan@debian.org Precedence: bulk X-list: linux-mips On Thu, Jun 30, 2005 at 06:09:09PM -0400, Stephen P. Becker wrote: > > > 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? I don't think glibc 2.3.5 worked for mips64. But I haven't checked it in a long time. Try CVS HEAD of glibc instead. Other than that, you're on your own - building glibc is extremely error prone. -- Daniel Jacobowitz CodeSourcery, LLC From mboxrd@z Thu Jan 1 00:00:00 1970 Received: with ECARTIS (v1.0.0; list linux-mips); Fri, 01 Jul 2005 05:41:09 +0100 (BST) Received: from sccrmhc11.comcast.net ([IPv6:::ffff:204.127.202.55]:58575 "EHLO sccrmhc11.comcast.net") by linux-mips.org with ESMTP id ; Fri, 1 Jul 2005 05:40:48 +0100 Received: from [192.168.1.4] (pcp0011842295pcs.waldrf01.md.comcast.net[69.251.97.45]) by comcast.net (sccrmhc11) with ESMTP id <2005070104403001100lsrpfe>; Fri, 1 Jul 2005 04:40:30 +0000 Message-ID: <42C4CA23.7080301@gentoo.org> Date: Fri, 01 Jul 2005 00:44:19 -0400 From: Kumba User-Agent: Mozilla Thunderbird 1.0.2 (Windows/20050317) X-Accept-Language: en-us, en MIME-Version: 1.0 To: linux-mips@linux-mips.org Subject: Re: Seg fault when compiled with -mabi=64 and -lpthread References: <20050630173409Z8226102-3678+735@linux-mips.org> <20050630202111.GC3245@linux-mips.org> <20050630210357.GA23456@nevyn.them.org> <42C46D85.9050104@gentoo.org> <20050701035105.GA9601@nevyn.them.org> In-Reply-To: <20050701035105.GA9601@nevyn.them.org> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Return-Path: X-Envelope-To: <"|/home/ecartis/ecartis -s linux-mips"> (uid 0) X-Orcpt: rfc822;linux-mips@linux-mips.org Original-Recipient: rfc822;linux-mips@linux-mips.org X-archive-position: 8284 X-ecartis-version: Ecartis v1.0.0 Sender: linux-mips-bounce@linux-mips.org Errors-to: linux-mips-bounce@linux-mips.org X-original-sender: kumba@gentoo.org Precedence: bulk X-list: linux-mips Daniel Jacobowitz wrote: > I don't think glibc 2.3.5 worked for mips64. But I haven't checked it > in a long time. Try CVS HEAD of glibc instead. > > Other than that, you're on your own - building glibc is extremely error > prone. > I'm thiking this is more a possible oddity/bug in the kernel. It may be glibc related, but I'm no concrete interpreter of strace output. That said, I tried geoman's conftest.c snippet in an o32/glibc userland, n32/glibc userland, and o32/uclibc userland just to see if there was any difference. The commonalities between all three was something is happening with rt_siguspend/sys32_rt_siguspend. In o32/glibc and o32/uclibc, calls to rt_sigsuspend returned EINTR (interrupted system call). o32 itself generates a silent SIGBUS (only seen in strace output. o32/uclibc seems to complete (reaches exit(0)), but its rt_sigsuspend calls were also returning EINTR. n32/glibc was the one that generates the Oops message (w/o locking the system up). The only differences was that o32/glibc and n32/glibc both SIGBUS/SIGSEG, while o32/uclibc seems to complete. This could point to a glibc problem. Below is the snipped output from strace and ksymoops on n32 (cause strace doesn't seem to work in n32 yet): o32/glibc: clone(child_stack=0x10003010, flags=CLONE_VM|CLONE_FS|CLONE_FILES|CLONE_SIGHAND) = 9954 write(4, "*\260b \0\0\0\5\0\0\0\0*\257\352H*\253\3H*\253\200\0\4"..., 148) = 148 rt_sigprocmask(SIG_SETMASK, NULL, [32], 16) = 0 write(4, "*\265\20\200\0\0\0\0\0\0\0\0\0@\10\240\0\0\0\0\200\0\0"..., 148) = 148 rt_sigprocmask(SIG_SETMASK, NULL, [32], 16) = 0 rt_siguspend([] --- SIGRT_0 (Unknown signal 32) @ 0 (0) --- <... rt_siguspend resumed> ) = -1 EINTR (Interrupted system call) sigreturn() = ? (mask now ~[HUP INT QUIT ILL IOT KILL BUS ALRM TERM USR1 CHLD PWR URG IO CONT TTOU PROF XFSZ 32 33 34 35 37 38 39 40 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 57 58 59 60 61 62 63 64 65 66 67 68 74 77 78 79 80 81 83 84 85 86 87 88 89 90 91 92 94 95 96 99 100 101 105 108 110 112 114 115 116 117 118 119 120 121 122 123 124 125 126]) --- SIGBUS (Bus error) @ 0 (0) --- +++ killed by SIGBUS +++ n32/glibc: >>$31; a80000002001abc4 >>PC; 00000000 Before first symbol Trace; a80000002001ade8 <_sys32_rt_sigsuspend+180/1a8> Trace; a80000002001e7f4 Trace; a80000002001e7f4 o32/uclibc: clone(child_stack=0x100030c0, flags=CLONE_VM|CLONE_FS|CLONE_FILES|CLONE_SIGHAND) = 10004 write(4, "\0\0\0\0\0\0\0\5\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0"..., 148) = 148 rt_sigprocmask(SIG_SETMASK, NULL, [RT_0], 16) = 0 write(4, "*\263\363\300\0\0\0\0\0\0\0\0\0@\0070\0\0\0\0\200\0\0\0"..., 148) = 148 rt_sigprocmask(SIG_SETMASK, NULL, [RT_0], 16) = 0 rt_siguspend([] --- SIGRT_0 (Unknown signal 32) @ 0 (0) --- <... rt_siguspend resumed> ) = -1 EINTR (Interrupted system call) sigreturn() = ? (mask now [TRAP IOT FPE BUS PIPE CHLD PROF RT_1 RT_3 RT_4 RT_5 RT_6 RT_7 RT_9 RT_10 RT_68 RT_69 RT_71 RT_72 RT_73]) rt_sigprocmask(SIG_SETMASK, NULL, [RT_0], 16) = 0 rt_siguspend([] --- SIGRT_0 (Unknown signal 32) @ 0 (0) --- <... rt_siguspend resumed> ) = -1 EINTR (Interrupted system call) sigreturn() = ? (mask now [TRAP IOT FPE BUS PIPE CHLD PROF RT_1 RT_3 RT_4 RT_5 RT_6 RT_7 RT_9 RT_10 RT_68 RT_69 RT_71 RT_72 RT_73]) write(4, "*\263\363\300\0\0\0\1\0\0\4\2\0@\0070\0\0\0\0\200\0\0\0"..., 148) = 148 write(4, "*\263\363\300\0\0\0\2\0\0\0\0*\2571T*\257iT*\257i\10\0"..., 148) = 148 rt_sigprocmask(SIG_SETMASK, NULL, [RT_0], 16) = 0 rt_siguspend([] --- SIGRT_0 (Unknown signal 32) @ 0 (0) --- <... rt_siguspend resumed> ) = -1 EINTR (Interrupted system call) sigreturn() = ? (mask now [TRAP IOT FPE BUS PIPE CHLD PROF RT_1 RT_3 RT_4 RT_5 RT_6 RT_7 RT_9 RT_10 RT_68 RT_69 RT_71 RT_72 RT_73]) wait4(10004, NULL, __WCLONE, NULL) = 10004 exit(0) = ? Thoughts? --Kumba -- Gentoo/MIPS Team Lead Gentoo Foundation Board of Trustees "Such is oft the course of deeds that move the wheels of the world: small hands do them because they must, while the eyes of the great are elsewhere." --Elrond From mboxrd@z Thu Jan 1 00:00:00 1970 Received: with ECARTIS (v1.0.0; list linux-mips); Fri, 01 Jul 2005 09:50:02 +0100 (BST) Received: from pollux.ds.pg.gda.pl ([IPv6:::ffff:153.19.208.7]:40970 "EHLO pollux.ds.pg.gda.pl") by linux-mips.org with ESMTP id ; Fri, 1 Jul 2005 09:49:47 +0100 Received: from localhost (localhost [127.0.0.1]) by pollux.ds.pg.gda.pl (Postfix) with ESMTP id 1B36FE1C8A; Fri, 1 Jul 2005 10:49:35 +0200 (CEST) Received: from pollux.ds.pg.gda.pl ([127.0.0.1]) by localhost (pollux [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 26253-10; Fri, 1 Jul 2005 10:49:34 +0200 (CEST) Received: from piorun.ds.pg.gda.pl (piorun.ds.pg.gda.pl [153.19.208.8]) by pollux.ds.pg.gda.pl (Postfix) with ESMTP id BABF4E1C78; Fri, 1 Jul 2005 10:49:34 +0200 (CEST) Received: from blysk.ds.pg.gda.pl (macro@blysk.ds.pg.gda.pl [153.19.208.6]) by piorun.ds.pg.gda.pl (8.13.3/8.13.1) with ESMTP id j618nZdd008825; Fri, 1 Jul 2005 10:49:36 +0200 Date: Fri, 1 Jul 2005 09:49:39 +0100 (BST) From: "Maciej W. Rozycki" To: Daniel Jacobowitz Cc: "Stephen P. Becker" , Ralf Baechle , Bryan Althouse , "'Linux/MIPS Development'" Subject: Re: Seg fault when compiled with -mabi=64 and -lpthread In-Reply-To: <20050701035105.GA9601@nevyn.them.org> Message-ID: References: <20050630173409Z8226102-3678+735@linux-mips.org> <20050630202111.GC3245@linux-mips.org> <20050630210357.GA23456@nevyn.them.org> <42C46D85.9050104@gentoo.org> <20050701035105.GA9601@nevyn.them.org> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-Virus-Scanned: ClamAV 0.85.1/962/Fri Jul 1 07:19:05 2005 on piorun.ds.pg.gda.pl X-Virus-Status: Clean X-Virus-Scanned: by amavisd-new at pollux.ds.pg.gda.pl Return-Path: X-Envelope-To: <"|/home/ecartis/ecartis -s linux-mips"> (uid 0) X-Orcpt: rfc822;linux-mips@linux-mips.org Original-Recipient: rfc822;linux-mips@linux-mips.org X-archive-position: 8290 X-ecartis-version: Ecartis v1.0.0 Sender: linux-mips-bounce@linux-mips.org Errors-to: linux-mips-bounce@linux-mips.org X-original-sender: macro@linux-mips.org Precedence: bulk X-list: linux-mips On Thu, 30 Jun 2005, Daniel Jacobowitz wrote: > > 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? > > I don't think glibc 2.3.5 worked for mips64. But I haven't checked it > in a long time. Try CVS HEAD of glibc instead. Well, I tried a few trivial programs that use libpthread in my (n)64 environment, which is based on 2.3.5, and they worked just fine. They could have bin as simple as `ls', but as I have seen in the original report you do not have to make extensive use of the library to trigger problematic behaviour. Though it can be related to patches I have applied, me having built glibc with GCC 4.0.0 or perhaps it only happens for BE... > Other than that, you're on your own - building glibc is extremely error > prone. And you may need external patches as glibc is (effectively) not maintained. Maciej From mboxrd@z Thu Jan 1 00:00:00 1970 Received: with ECARTIS (v1.0.0; list linux-mips); Fri, 01 Jul 2005 14:39:39 +0100 (BST) Received: from nevyn.them.org ([IPv6:::ffff:66.93.172.17]:56800 "EHLO nevyn.them.org") by linux-mips.org with ESMTP id ; Fri, 1 Jul 2005 14:39:24 +0100 Received: from drow by nevyn.them.org with local (Exim 4.51) id 1DoLja-0006Rz-O8; Fri, 01 Jul 2005 09:39:10 -0400 Date: Fri, 1 Jul 2005 09:39:10 -0400 From: Daniel Jacobowitz To: "Maciej W. Rozycki" Cc: "Stephen P. Becker" , Ralf Baechle , Bryan Althouse , 'Linux/MIPS Development' Subject: Re: Seg fault when compiled with -mabi=64 and -lpthread Message-ID: <20050701133910.GA24716@nevyn.them.org> References: <20050630173409Z8226102-3678+735@linux-mips.org> <20050630202111.GC3245@linux-mips.org> <20050630210357.GA23456@nevyn.them.org> <42C46D85.9050104@gentoo.org> <20050701035105.GA9601@nevyn.them.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.5.8i Return-Path: X-Envelope-To: <"|/home/ecartis/ecartis -s linux-mips"> (uid 0) X-Orcpt: rfc822;linux-mips@linux-mips.org Original-Recipient: rfc822;linux-mips@linux-mips.org X-archive-position: 8300 X-ecartis-version: Ecartis v1.0.0 Sender: linux-mips-bounce@linux-mips.org Errors-to: linux-mips-bounce@linux-mips.org X-original-sender: dan@debian.org Precedence: bulk X-list: linux-mips On Fri, Jul 01, 2005 at 09:49:39AM +0100, Maciej W. Rozycki wrote: > And you may need external patches as glibc is (effectively) not > maintained. Shall I just stop trying, then? I'm getting tired of arguing with you about this. For the twentieth time: I am doing everything I can to keep glibc HEAD building for MIPS. I do not have the time or energy to deal with Roland's restrictive stable branch rules, so I can not help with 2.3.5. But if you encounter a problem on HEAD, let me know, and I will either fix it myself or (if you've got a patch) pester people relentlessly until it is applied. -- Daniel Jacobowitz CodeSourcery, LLC From mboxrd@z Thu Jan 1 00:00:00 1970 Received: with ECARTIS (v1.0.0; list linux-mips); Fri, 01 Jul 2005 15:11:09 +0100 (BST) Received: from pollux.ds.pg.gda.pl ([IPv6:::ffff:153.19.208.7]:26630 "EHLO pollux.ds.pg.gda.pl") by linux-mips.org with ESMTP id ; Fri, 1 Jul 2005 15:10:51 +0100 Received: from localhost (localhost [127.0.0.1]) by pollux.ds.pg.gda.pl (Postfix) with ESMTP id 7A8C0F5999; Fri, 1 Jul 2005 16:10:38 +0200 (CEST) Received: from pollux.ds.pg.gda.pl ([127.0.0.1]) by localhost (pollux [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 05091-10; Fri, 1 Jul 2005 16:10:38 +0200 (CEST) Received: from piorun.ds.pg.gda.pl (piorun.ds.pg.gda.pl [153.19.208.8]) by pollux.ds.pg.gda.pl (Postfix) with ESMTP id 29565F598E; Fri, 1 Jul 2005 16:10:38 +0200 (CEST) Received: from blysk.ds.pg.gda.pl (macro@blysk.ds.pg.gda.pl [153.19.208.6]) by piorun.ds.pg.gda.pl (8.13.3/8.13.1) with ESMTP id j61EA0n6004138; Fri, 1 Jul 2005 16:10:00 +0200 Date: Fri, 1 Jul 2005 15:10:08 +0100 (BST) From: "Maciej W. Rozycki" To: Daniel Jacobowitz Cc: "Stephen P. Becker" , Ralf Baechle , Bryan Althouse , "'Linux/MIPS Development'" Subject: Re: Seg fault when compiled with -mabi=64 and -lpthread In-Reply-To: <20050701133910.GA24716@nevyn.them.org> Message-ID: References: <20050630173409Z8226102-3678+735@linux-mips.org> <20050630202111.GC3245@linux-mips.org> <20050630210357.GA23456@nevyn.them.org> <42C46D85.9050104@gentoo.org> <20050701035105.GA9601@nevyn.them.org> <20050701133910.GA24716@nevyn.them.org> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-Virus-Scanned: ClamAV 0.85.1/963/Fri Jul 1 15:27:29 2005 on piorun.ds.pg.gda.pl X-Virus-Status: Clean X-Virus-Scanned: by amavisd-new at pollux.ds.pg.gda.pl Return-Path: X-Envelope-To: <"|/home/ecartis/ecartis -s linux-mips"> (uid 0) X-Orcpt: rfc822;linux-mips@linux-mips.org Original-Recipient: rfc822;linux-mips@linux-mips.org X-archive-position: 8302 X-ecartis-version: Ecartis v1.0.0 Sender: linux-mips-bounce@linux-mips.org Errors-to: linux-mips-bounce@linux-mips.org X-original-sender: macro@linux-mips.org Precedence: bulk X-list: linux-mips On Fri, 1 Jul 2005, Daniel Jacobowitz wrote: > > And you may need external patches as glibc is (effectively) not > > maintained. > > Shall I just stop trying, then? I'm getting tired of arguing with you > about this. Certainly not! -- in this case I haven't meant the MIPS port, but glibc as a whole -- just have a look at the response to fixes for the Alpha or i386! And please forgive me for the feeling of me arguing with you -- it wasn't my intention. Frankly I cannot even realize exactly when it happened. > For the twentieth time: I am doing everything I can to keep glibc HEAD > building for MIPS. I do not have the time or energy to deal with > Roland's restrictive stable branch rules, so I can not help with 2.3.5. Building is not everything. ;-) > But if you encounter a problem on HEAD, let me know, and I will either > fix it myself or (if you've got a patch) pester people relentlessly > until it is applied. Certainly -- I'm assuming you are ready for a pile of patches then? Well, perhaps not that many, but I think I've got around four that should go upstream. I'll have a look if they apply cleanly. None of them addresses a problem with building though. Maciej From mboxrd@z Thu Jan 1 00:00:00 1970 Received: with ECARTIS (v1.0.0; list linux-mips); Fri, 01 Jul 2005 15:47:07 +0100 (BST) Received: from nevyn.them.org ([IPv6:::ffff:66.93.172.17]:53191 "EHLO nevyn.them.org") by linux-mips.org with ESMTP id ; Fri, 1 Jul 2005 15:46:49 +0100 Received: from drow by nevyn.them.org with local (Exim 4.51) id 1DoMmu-00080D-7B; Fri, 01 Jul 2005 10:46:40 -0400 Date: Fri, 1 Jul 2005 10:46:40 -0400 From: Daniel Jacobowitz To: "Maciej W. Rozycki" Cc: "Stephen P. Becker" , Ralf Baechle , Bryan Althouse , 'Linux/MIPS Development' Subject: Re: Seg fault when compiled with -mabi=64 and -lpthread Message-ID: <20050701144640.GA30720@nevyn.them.org> References: <20050630173409Z8226102-3678+735@linux-mips.org> <20050630202111.GC3245@linux-mips.org> <20050630210357.GA23456@nevyn.them.org> <42C46D85.9050104@gentoo.org> <20050701035105.GA9601@nevyn.them.org> <20050701133910.GA24716@nevyn.them.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.5.8i Return-Path: X-Envelope-To: <"|/home/ecartis/ecartis -s linux-mips"> (uid 0) X-Orcpt: rfc822;linux-mips@linux-mips.org Original-Recipient: rfc822;linux-mips@linux-mips.org X-archive-position: 8304 X-ecartis-version: Ecartis v1.0.0 Sender: linux-mips-bounce@linux-mips.org Errors-to: linux-mips-bounce@linux-mips.org X-original-sender: dan@debian.org Precedence: bulk X-list: linux-mips On Fri, Jul 01, 2005 at 03:10:08PM +0100, Maciej W. Rozycki wrote: > Certainly -- I'm assuming you are ready for a pile of patches then? > Well, perhaps not that many, but I think I've got around four that should > go upstream. I'll have a look if they apply cleanly. None of them > addresses a problem with building though. Sure - send them to me, or better yet, put them in bugzilla and make sure you copy me. I can't promise you timely response just now because I'm about twelve feet under on this current project at work, but I'll do everything I can. We're going to have automated MIPS regression testing sometime this year, too. -- Daniel Jacobowitz CodeSourcery, LLC From mboxrd@z Thu Jan 1 00:00:00 1970 Received: with ECARTIS (v1.0.0; list linux-mips); Fri, 01 Jul 2005 15:58:16 +0100 (BST) Received: from lennier.cc.vt.edu ([IPv6:::ffff:198.82.162.213]:11213 "EHLO lennier.cc.vt.edu") by linux-mips.org with ESMTP id ; Fri, 1 Jul 2005 15:57:56 +0100 Received: from dagger.cc.vt.edu (IDENT:mirapoint@[10.1.1.11]) by lennier.cc.vt.edu (8.12.11/8.12.11) with ESMTP id j61EuVpO006465; Fri, 1 Jul 2005 10:56:41 -0400 Received: from [128.173.184.73] (gs4073.geos.vt.edu [128.173.184.73]) by dagger.cc.vt.edu (MOS 3.6.4-CR) with ESMTP id DOU46020; Fri, 1 Jul 2005 10:56:24 -0400 (EDT) Message-ID: <42C55991.70109@gentoo.org> Date: Fri, 01 Jul 2005 10:56:17 -0400 From: "Stephen P. Becker" User-Agent: Mozilla Thunderbird 1.0.2 (X11/20050624) X-Accept-Language: en-us, en MIME-Version: 1.0 To: Daniel Jacobowitz CC: Ralf Baechle , Bryan Althouse , "'Linux/MIPS Development'" Subject: Re: Seg fault when compiled with -mabi=64 and -lpthread References: <20050630173409Z8226102-3678+735@linux-mips.org> <20050630202111.GC3245@linux-mips.org> <20050630210357.GA23456@nevyn.them.org> <42C46D85.9050104@gentoo.org> <20050701035105.GA9601@nevyn.them.org> In-Reply-To: <20050701035105.GA9601@nevyn.them.org> Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Return-Path: X-Envelope-To: <"|/home/ecartis/ecartis -s linux-mips"> (uid 0) X-Orcpt: rfc822;linux-mips@linux-mips.org Original-Recipient: rfc822;linux-mips@linux-mips.org X-archive-position: 8305 X-ecartis-version: Ecartis v1.0.0 Sender: linux-mips-bounce@linux-mips.org Errors-to: linux-mips-bounce@linux-mips.org X-original-sender: geoman@gentoo.org Precedence: bulk X-list: linux-mips >>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? > > > I don't think glibc 2.3.5 worked for mips64. But I haven't checked it > in a long time. Try CVS HEAD of glibc instead. > > Other than that, you're on your own - building glibc is extremely error > prone. > I'm sure it can be error prone, but that isn't the problem here at all. My n32 glibc 2.3.5 compiled and seems to work just fine, and I was able to compile an entire userland around it that has no (other) problems so far as I can tell. By this, I mean "emerge system" in Gentoo terms, which is a pretty good test of whether the toolchain works or not. Furthermore, other programs that are linked against libpthread run without causing a segfault and oops. I'm talking about glib, as in the glib that used to be part of GTK+ before it was split out some time ago. The segfault with kernel oops that I can't get around occurs while glib's configure script is checking for libpthread. Specifically, it links http://beerandrocks.net:8080/~spbecker/oops/conftest.c against libpthread and then runs it. I've somewhat convinced myself this is either a kernel and/or a header problem. It seems I'm only able to reproduce this problem when trying to compile and run that code while running 2.6.12 from cvs. As I previously mentioned, I tested the offending code on a kernel I compiled from a 2.6.10 snapshot some time ago, and it ran with no segfault or oops. -Steve From mboxrd@z Thu Jan 1 00:00:00 1970 Received: with ECARTIS (v1.0.0; list linux-mips); Fri, 01 Jul 2005 16:07:45 +0100 (BST) Received: from pollux.ds.pg.gda.pl ([IPv6:::ffff:153.19.208.7]:61190 "EHLO pollux.ds.pg.gda.pl") by linux-mips.org with ESMTP id ; Fri, 1 Jul 2005 16:07:25 +0100 Received: from localhost (localhost [127.0.0.1]) by pollux.ds.pg.gda.pl (Postfix) with ESMTP id BE155F59AB; Fri, 1 Jul 2005 17:07:13 +0200 (CEST) Received: from pollux.ds.pg.gda.pl ([127.0.0.1]) by localhost (pollux [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 06978-06; Fri, 1 Jul 2005 17:07:13 +0200 (CEST) Received: from piorun.ds.pg.gda.pl (piorun.ds.pg.gda.pl [153.19.208.8]) by pollux.ds.pg.gda.pl (Postfix) with ESMTP id 8EB33F599C; Fri, 1 Jul 2005 17:07:13 +0200 (CEST) Received: from blysk.ds.pg.gda.pl (macro@blysk.ds.pg.gda.pl [153.19.208.6]) by piorun.ds.pg.gda.pl (8.13.3/8.13.1) with ESMTP id j61F47tZ007207; Fri, 1 Jul 2005 17:07:10 +0200 Date: Fri, 1 Jul 2005 16:04:15 +0100 (BST) From: "Maciej W. Rozycki" To: Daniel Jacobowitz Cc: "Stephen P. Becker" , Ralf Baechle , Bryan Althouse , "'Linux/MIPS Development'" Subject: Re: Seg fault when compiled with -mabi=64 and -lpthread In-Reply-To: <20050701144640.GA30720@nevyn.them.org> Message-ID: References: <20050630173409Z8226102-3678+735@linux-mips.org> <20050630202111.GC3245@linux-mips.org> <20050630210357.GA23456@nevyn.them.org> <42C46D85.9050104@gentoo.org> <20050701035105.GA9601@nevyn.them.org> <20050701133910.GA24716@nevyn.them.org> <20050701144640.GA30720@nevyn.them.org> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-Virus-Scanned: ClamAV 0.85.1/963/Fri Jul 1 15:27:29 2005 on piorun.ds.pg.gda.pl X-Virus-Status: Clean X-Virus-Scanned: by amavisd-new at pollux.ds.pg.gda.pl Return-Path: X-Envelope-To: <"|/home/ecartis/ecartis -s linux-mips"> (uid 0) X-Orcpt: rfc822;linux-mips@linux-mips.org Original-Recipient: rfc822;linux-mips@linux-mips.org X-archive-position: 8306 X-ecartis-version: Ecartis v1.0.0 Sender: linux-mips-bounce@linux-mips.org Errors-to: linux-mips-bounce@linux-mips.org X-original-sender: macro@linux-mips.org Precedence: bulk X-list: linux-mips On Fri, 1 Jul 2005, Daniel Jacobowitz wrote: > Sure - send them to me, or better yet, put them in bugzilla and make > sure you copy me. I can't promise you timely response just now because > I'm about twelve feet under on this current project at work, but I'll > do everything I can. OK, one is already there as bug #933 and I'll add the rest. > We're going to have automated MIPS regression testing sometime this > year, too. Oh, that would be most welcome. Maciej From mboxrd@z Thu Jan 1 00:00:00 1970 Received: with ECARTIS (v1.0.0; list linux-mips); Fri, 01 Jul 2005 16:09:58 +0100 (BST) Received: from sccrmhc14.comcast.net ([IPv6:::ffff:204.127.202.59]:39159 "EHLO sccrmhc14.comcast.net") by linux-mips.org with ESMTP id ; Fri, 1 Jul 2005 16:09:38 +0100 Received: from ba3pi (pcp0010731669pcs.howard01.md.comcast.net[69.243.71.130]) by comcast.net (sccrmhc14) with SMTP id <20050701150924014004f2s2e>; Fri, 1 Jul 2005 15:09:25 +0000 From: "Bryan Althouse" To: "'Daniel Jacobowitz'" , "'Stephen P. Becker'" , Cc: "'Linux/MIPS Development'" Subject: RE: Seg fault when compiled with -mabi=64 and -lpthread Date: Fri, 1 Jul 2005 11:09:22 -0400 MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit X-Mailer: Microsoft Office Outlook, Build 11.0.6353 X-MIMEOLE: Produced By Microsoft MimeOLE V6.00.2900.2180 Thread-index: AcV98BzgA6st/adyScio+YU2hd//HgAW8vUw In-Reply-To: <20050701035105.GA9601@nevyn.them.org> Message-Id: <20050701150938Z8226157-3678+821@linux-mips.org> Return-Path: X-Envelope-To: <"|/home/ecartis/ecartis -s linux-mips"> (uid 0) X-Orcpt: rfc822;linux-mips@linux-mips.org Original-Recipient: rfc822;linux-mips@linux-mips.org X-archive-position: 8307 X-ecartis-version: Ecartis v1.0.0 Sender: linux-mips-bounce@linux-mips.org Errors-to: linux-mips-bounce@linux-mips.org X-original-sender: bryan.althouse@3phoenix.com Precedence: bulk X-list: linux-mips Thanks for everyone's input! Looks like I should upgrade glibc, and possibly gcc. When you say that I should try CVS HEAD of glibc, I'm not sure what you mean. I have looked in the linux-mips.org CVS and the closest thing I can find is libc, and it looks really old. I have also found a glibc CVS at :pserver:anoncvs@sources.redhat.com:/cvs/glibc. If I get libc from here is this the "CVS HEAD"? Should I get GCC from the generic GCC site, or should get it from the linux-mips CVS? I apologize for the simple questions. I have not built a tool chain before. I've been using the one supplied by PMC-Sierra. Will I need to patch any of these sources for MIPs? Bryan -----Original Message----- From: Daniel Jacobowitz [mailto:dan@debian.org] Sent: Thursday, June 30, 2005 11:51 PM To: Stephen P. Becker Cc: Ralf Baechle; Bryan Althouse; 'Linux/MIPS Development' Subject: Re: Seg fault when compiled with -mabi=64 and -lpthread On Thu, Jun 30, 2005 at 06:09:09PM -0400, Stephen P. Becker wrote: > > > 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? I don't think glibc 2.3.5 worked for mips64. But I haven't checked it in a long time. Try CVS HEAD of glibc instead. Other than that, you're on your own - building glibc is extremely error prone. -- Daniel Jacobowitz CodeSourcery, LLC From mboxrd@z Thu Jan 1 00:00:00 1970 Received: with ECARTIS (v1.0.0; list linux-mips); Fri, 01 Jul 2005 16:22:37 +0100 (BST) Received: from pollux.ds.pg.gda.pl ([IPv6:::ffff:153.19.208.7]:45577 "EHLO pollux.ds.pg.gda.pl") by linux-mips.org with ESMTP id ; Fri, 1 Jul 2005 16:22:20 +0100 Received: from localhost (localhost [127.0.0.1]) by pollux.ds.pg.gda.pl (Postfix) with ESMTP id 24E09F598F; Fri, 1 Jul 2005 17:22:08 +0200 (CEST) Received: from pollux.ds.pg.gda.pl ([127.0.0.1]) by localhost (pollux [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 02511-05; Fri, 1 Jul 2005 17:22:08 +0200 (CEST) Received: from piorun.ds.pg.gda.pl (piorun.ds.pg.gda.pl [153.19.208.8]) by pollux.ds.pg.gda.pl (Postfix) with ESMTP id D8C1EF598D; Fri, 1 Jul 2005 17:22:07 +0200 (CEST) Received: from blysk.ds.pg.gda.pl (macro@blysk.ds.pg.gda.pl [153.19.208.6]) by piorun.ds.pg.gda.pl (8.13.3/8.13.1) with ESMTP id j61FMAN2008141; Fri, 1 Jul 2005 17:22:11 +0200 Date: Fri, 1 Jul 2005 16:22:19 +0100 (BST) From: "Maciej W. Rozycki" To: "Stephen P. Becker" Cc: Daniel Jacobowitz , Ralf Baechle , Bryan Althouse , "'Linux/MIPS Development'" Subject: Re: Seg fault when compiled with -mabi=64 and -lpthread In-Reply-To: <42C55991.70109@gentoo.org> Message-ID: References: <20050630173409Z8226102-3678+735@linux-mips.org> <20050630202111.GC3245@linux-mips.org> <20050630210357.GA23456@nevyn.them.org> <42C46D85.9050104@gentoo.org> <20050701035105.GA9601@nevyn.them.org> <42C55991.70109@gentoo.org> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-Virus-Scanned: ClamAV 0.85.1/963/Fri Jul 1 15:27:29 2005 on piorun.ds.pg.gda.pl X-Virus-Status: Clean X-Virus-Scanned: by amavisd-new at pollux.ds.pg.gda.pl Return-Path: X-Envelope-To: <"|/home/ecartis/ecartis -s linux-mips"> (uid 0) X-Orcpt: rfc822;linux-mips@linux-mips.org Original-Recipient: rfc822;linux-mips@linux-mips.org X-archive-position: 8308 X-ecartis-version: Ecartis v1.0.0 Sender: linux-mips-bounce@linux-mips.org Errors-to: linux-mips-bounce@linux-mips.org X-original-sender: macro@linux-mips.org Precedence: bulk X-list: linux-mips On Fri, 1 Jul 2005, Stephen P. Becker wrote: > I'm sure it can be error prone, but that isn't the problem here at all. > My n32 glibc 2.3.5 compiled and seems to work just fine, and I was > able to compile an entire userland around it that has no (other) > problems so far as I can tell. By this, I mean "emerge system" in > Gentoo terms, which is a pretty good test of whether the toolchain works > or not. Furthermore, other programs that are linked against libpthread > run without causing a segfault and oops. I'm talking about glib, as in > the glib that used to be part of GTK+ before it was split out some time > ago. > > The segfault with kernel oops that I can't get around occurs while > glib's configure script is checking for libpthread. Specifically, it > links http://beerandrocks.net:8080/~spbecker/oops/conftest.c against > libpthread and then runs it. And libpthread is part of glibc, not glib. So if an autoconf test (which I'm assuming is AC_CHECK_LIB() rather than a hand-crafted hack) breaks on running a program linked against libpthread, then it's not a problem with glib, but probably with either glibc or the toolchain used. > I've somewhat convinced myself this is either a kernel and/or a header > problem. It seems I'm only able to reproduce this problem when trying > to compile and run that code while running 2.6.12 from cvs. As I > previously mentioned, I tested the offending code on a kernel I compiled > from a 2.6.10 snapshot some time ago, and it ran with no segfault or oops. If you get an Oops when running software as non-root, then it's a kernel bug, no matter what. Maciej From mboxrd@z Thu Jan 1 00:00:00 1970 Received: with ECARTIS (v1.0.0; list linux-mips); Fri, 01 Jul 2005 16:29:48 +0100 (BST) Received: from pollux.ds.pg.gda.pl ([IPv6:::ffff:153.19.208.7]:62736 "EHLO pollux.ds.pg.gda.pl") by linux-mips.org with ESMTP id ; Fri, 1 Jul 2005 16:29:31 +0100 Received: from localhost (localhost [127.0.0.1]) by pollux.ds.pg.gda.pl (Postfix) with ESMTP id 07967F598F; Fri, 1 Jul 2005 17:29:19 +0200 (CEST) Received: from pollux.ds.pg.gda.pl ([127.0.0.1]) by localhost (pollux [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 14038-09; Fri, 1 Jul 2005 17:29:18 +0200 (CEST) Received: from piorun.ds.pg.gda.pl (piorun.ds.pg.gda.pl [153.19.208.8]) by pollux.ds.pg.gda.pl (Postfix) with ESMTP id BE05CF598D; Fri, 1 Jul 2005 17:29:18 +0200 (CEST) Received: from blysk.ds.pg.gda.pl (macro@blysk.ds.pg.gda.pl [153.19.208.6]) by piorun.ds.pg.gda.pl (8.13.3/8.13.1) with ESMTP id j61FTMYd008310; Fri, 1 Jul 2005 17:29:22 +0200 Date: Fri, 1 Jul 2005 16:29:30 +0100 (BST) From: "Maciej W. Rozycki" To: Bryan Althouse Cc: "'Daniel Jacobowitz'" , "'Stephen P. Becker'" , macro@blysk.ds.pg.gda.pl, "'Linux/MIPS Development'" Subject: RE: Seg fault when compiled with -mabi=64 and -lpthread In-Reply-To: <20050701150938Z8226157-3678+821@linux-mips.org> Message-ID: References: <20050701150938Z8226157-3678+821@linux-mips.org> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-Virus-Scanned: ClamAV 0.85.1/963/Fri Jul 1 15:27:29 2005 on piorun.ds.pg.gda.pl X-Virus-Status: Clean X-Virus-Scanned: by amavisd-new at pollux.ds.pg.gda.pl Return-Path: X-Envelope-To: <"|/home/ecartis/ecartis -s linux-mips"> (uid 0) X-Orcpt: rfc822;linux-mips@linux-mips.org Original-Recipient: rfc822;linux-mips@linux-mips.org X-archive-position: 8309 X-ecartis-version: Ecartis v1.0.0 Sender: linux-mips-bounce@linux-mips.org Errors-to: linux-mips-bounce@linux-mips.org X-original-sender: macro@linux-mips.org Precedence: bulk X-list: linux-mips On Fri, 1 Jul 2005, Bryan Althouse wrote: > Looks like I should upgrade glibc, and possibly gcc. When you say that I > should try CVS HEAD of glibc, I'm not sure what you mean. I have looked in > the linux-mips.org CVS and the closest thing I can find is libc, and it > looks really old. I have also found a glibc CVS at > :pserver:anoncvs@sources.redhat.com:/cvs/glibc. If I get libc from here is > this the "CVS HEAD"? Yes, just pull the tree without any tags. > Should I get GCC from the generic GCC site, or should get it from the > linux-mips CVS? The latest GCC 3.4.x should probably be OK, but if you want 4.x, then just get the latest release from (your closest mirror of) ftp.gnu.org -- if you don't rush, that may be 4.0.1. > I apologize for the simple questions. I have not built a tool chain before. > I've been using the one supplied by PMC-Sierra. Will I need to patch any of > these sources for MIPs? It depends on whether you trigger any bugs. Maciej From mboxrd@z Thu Jan 1 00:00:00 1970 Received: with ECARTIS (v1.0.0; list linux-mips); Fri, 01 Jul 2005 16:54:37 +0100 (BST) Received: from eth13.com-link.com ([IPv6:::ffff:208.242.241.164]:34528 "EHLO real.realitydiluted.com") by linux-mips.org with ESMTP id ; Fri, 1 Jul 2005 16:54:16 +0100 Received: from sjhill by real.realitydiluted.com with local (Exim 4.50 #1 (Debian)) id 1DoMu9-0007J0-62; Fri, 01 Jul 2005 09:54:09 -0500 Subject: Re: Seg fault when compiled with -mabi=64 and -lpthread In-Reply-To: <20050701150938Z8226157-3678+821@linux-mips.org> To: Bryan Althouse Date: Fri, 1 Jul 2005 09:54:09 -0500 (CDT) CC: "'Daniel Jacobowitz'" , "'Stephen P. Becker'" , macro@blysk.ds.pg.gda.pl, "'Linux/MIPS Development'" X-Mailer: ELM [version 2.4ME+ PL100 (25)] MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Type: text/plain; charset=US-ASCII Message-Id: From: sjhill@realitydiluted.com Return-Path: X-Envelope-To: <"|/home/ecartis/ecartis -s linux-mips"> (uid 0) X-Orcpt: rfc822;linux-mips@linux-mips.org Original-Recipient: rfc822;linux-mips@linux-mips.org X-archive-position: 8311 X-ecartis-version: Ecartis v1.0.0 Sender: linux-mips-bounce@linux-mips.org Errors-to: linux-mips-bounce@linux-mips.org X-original-sender: sjhill@realitydiluted.com Precedence: bulk X-list: linux-mips > Looks like I should upgrade glibc, and possibly gcc. When you say that I > should try CVS HEAD of glibc, I'm not sure what you mean. I have looked in > the linux-mips.org CVS and the closest thing I can find is libc, and it > looks really old. I have also found a glibc CVS at > :pserver:anoncvs@sources.redhat.com:/cvs/glibc. If I get libc from here is > this the "CVS HEAD"? > > Should I get GCC from the generic GCC site, or should get it from the > linux-mips CVS? > > I apologize for the simple questions. I have not built a tool chain before. > I've been using the one supplied by PMC-Sierra. Will I need to patch any of > these sources for MIPs? > Also, stay away from the HEAD of GCC CVS. GCC-4.1.0 compilers cannot build Linux kernels. -Steve From mboxrd@z Thu Jan 1 00:00:00 1970 Received: with ECARTIS (v1.0.0; list linux-mips); Fri, 01 Jul 2005 17:41:40 +0100 (BST) Received: from lennier.cc.vt.edu ([IPv6:::ffff:198.82.162.213]:42939 "EHLO lennier.cc.vt.edu") by linux-mips.org with ESMTP id ; Fri, 1 Jul 2005 17:41:20 +0100 Received: from zidane.cc.vt.edu (IDENT:mirapoint@[10.1.1.13]) by lennier.cc.vt.edu (8.12.11/8.12.11) with ESMTP id j61Gdqm7005445; Fri, 1 Jul 2005 12:40:02 -0400 Received: from [128.173.184.73] (gs4073.geos.vt.edu [128.173.184.73]) by zidane.cc.vt.edu (MOS 3.6.4-CR) with ESMTP id DMZ68355; Fri, 1 Jul 2005 12:39:38 -0400 (EDT) Message-ID: <42C571C3.1060703@gentoo.org> Date: Fri, 01 Jul 2005 12:39:31 -0400 From: "Stephen P. Becker" User-Agent: Mozilla Thunderbird 1.0.2 (X11/20050624) X-Accept-Language: en-us, en MIME-Version: 1.0 To: "Maciej W. Rozycki" CC: Daniel Jacobowitz , Ralf Baechle , Bryan Althouse , "'Linux/MIPS Development'" Subject: Re: Seg fault when compiled with -mabi=64 and -lpthread References: <20050630173409Z8226102-3678+735@linux-mips.org> <20050630202111.GC3245@linux-mips.org> <20050630210357.GA23456@nevyn.them.org> <42C46D85.9050104@gentoo.org> <20050701035105.GA9601@nevyn.them.org> <42C55991.70109@gentoo.org> In-Reply-To: Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Return-Path: X-Envelope-To: <"|/home/ecartis/ecartis -s linux-mips"> (uid 0) X-Orcpt: rfc822;linux-mips@linux-mips.org Original-Recipient: rfc822;linux-mips@linux-mips.org X-archive-position: 8313 X-ecartis-version: Ecartis v1.0.0 Sender: linux-mips-bounce@linux-mips.org Errors-to: linux-mips-bounce@linux-mips.org X-original-sender: geoman@gentoo.org Precedence: bulk X-list: linux-mips >>The segfault with kernel oops that I can't get around occurs while >>glib's configure script is checking for libpthread. Specifically, it >>links http://beerandrocks.net:8080/~spbecker/oops/conftest.c against >>libpthread and then runs it. > > > And libpthread is part of glibc, not glib. So if an autoconf test (which > I'm assuming is AC_CHECK_LIB() rather than a hand-crafted hack) breaks on > running a program linked against libpthread, then it's not a problem with > glib, but probably with either glibc or the toolchain used. I'm aware of this. It just sounded like Daniel was questioning whether or not my glibc was compiling/working in the first place. >>I've somewhat convinced myself this is either a kernel and/or a header >>problem. It seems I'm only able to reproduce this problem when trying >>to compile and run that code while running 2.6.12 from cvs. As I >>previously mentioned, I tested the offending code on a kernel I compiled >>from a 2.6.10 snapshot some time ago, and it ran with no segfault or oops. > > > If you get an Oops when running software as non-root, then it's a kernel > bug, no matter what. > Yes, it certainly happens when running as a non-privileged user. If I get a bit of time later today, I was going to try and track down which cvs commit and/or kernel version broke things. -Steve From mboxrd@z Thu Jan 1 00:00:00 1970 Received: with ECARTIS (v1.0.0; list linux-mips); Fri, 01 Jul 2005 18:03:28 +0100 (BST) Received: from nevyn.them.org ([IPv6:::ffff:66.93.172.17]:24267 "EHLO nevyn.them.org") by linux-mips.org with ESMTP id ; Fri, 1 Jul 2005 18:03:09 +0100 Received: from drow by nevyn.them.org with local (Exim 4.51) id 1DoOuo-0005r2-Kn; Fri, 01 Jul 2005 13:02:58 -0400 Date: Fri, 1 Jul 2005 13:02:58 -0400 From: Daniel Jacobowitz To: "Stephen P. Becker" Cc: Ralf Baechle , Bryan Althouse , 'Linux/MIPS Development' Subject: Re: Seg fault when compiled with -mabi=64 and -lpthread Message-ID: <20050701170258.GA22405@nevyn.them.org> References: <20050630173409Z8226102-3678+735@linux-mips.org> <20050630202111.GC3245@linux-mips.org> <20050630210357.GA23456@nevyn.them.org> <42C46D85.9050104@gentoo.org> <20050701035105.GA9601@nevyn.them.org> <42C55991.70109@gentoo.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <42C55991.70109@gentoo.org> User-Agent: Mutt/1.5.8i Return-Path: X-Envelope-To: <"|/home/ecartis/ecartis -s linux-mips"> (uid 0) X-Orcpt: rfc822;linux-mips@linux-mips.org Original-Recipient: rfc822;linux-mips@linux-mips.org X-archive-position: 8315 X-ecartis-version: Ecartis v1.0.0 Sender: linux-mips-bounce@linux-mips.org Errors-to: linux-mips-bounce@linux-mips.org X-original-sender: dan@debian.org Precedence: bulk X-list: linux-mips On Fri, Jul 01, 2005 at 10:56:17AM -0400, Stephen P. Becker wrote: > The segfault with kernel oops that I can't get around occurs while > glib's configure script is checking for libpthread. Specifically, it > links http://beerandrocks.net:8080/~spbecker/oops/conftest.c against > libpthread and then runs it. If that oopses, your famed emerge testing hasn't run any threaded programs, my friend :-) Could be kernel, could be library, could be both. Must be at least kernel because the kernel should never oops. -- Daniel Jacobowitz CodeSourcery, LLC From mboxrd@z Thu Jan 1 00:00:00 1970 Received: with ECARTIS (v1.0.0; list linux-mips); Fri, 01 Jul 2005 18:17:36 +0100 (BST) Received: from lennier.cc.vt.edu ([IPv6:::ffff:198.82.162.213]:8924 "EHLO lennier.cc.vt.edu") by linux-mips.org with ESMTP id ; Fri, 1 Jul 2005 18:17:20 +0100 Received: from vivi.cc.vt.edu (IDENT:mirapoint@[10.1.1.12]) by lennier.cc.vt.edu (8.12.11/8.12.11) with ESMTP id j61HG0Qx017070; Fri, 1 Jul 2005 13:16:10 -0400 Received: from [128.173.184.73] (gs4073.geos.vt.edu [128.173.184.73]) by vivi.cc.vt.edu (MOS 3.6.4-CR) with ESMTP id DNQ77670; Fri, 1 Jul 2005 13:15:45 -0400 (EDT) Message-ID: <42C57A2E.4070702@gentoo.org> Date: Fri, 01 Jul 2005 13:15:26 -0400 From: "Stephen P. Becker" User-Agent: Mozilla Thunderbird 1.0.2 (X11/20050624) X-Accept-Language: en-us, en MIME-Version: 1.0 To: Daniel Jacobowitz CC: Ralf Baechle , Bryan Althouse , "'Linux/MIPS Development'" Subject: Re: Seg fault when compiled with -mabi=64 and -lpthread References: <20050630173409Z8226102-3678+735@linux-mips.org> <20050630202111.GC3245@linux-mips.org> <20050630210357.GA23456@nevyn.them.org> <42C46D85.9050104@gentoo.org> <20050701035105.GA9601@nevyn.them.org> <42C55991.70109@gentoo.org> <20050701170258.GA22405@nevyn.them.org> In-Reply-To: <20050701170258.GA22405@nevyn.them.org> Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Return-Path: X-Envelope-To: <"|/home/ecartis/ecartis -s linux-mips"> (uid 0) X-Orcpt: rfc822;linux-mips@linux-mips.org Original-Recipient: rfc822;linux-mips@linux-mips.org X-archive-position: 8316 X-ecartis-version: Ecartis v1.0.0 Sender: linux-mips-bounce@linux-mips.org Errors-to: linux-mips-bounce@linux-mips.org X-original-sender: geoman@gentoo.org Precedence: bulk X-list: linux-mips Daniel Jacobowitz wrote: > On Fri, Jul 01, 2005 at 10:56:17AM -0400, Stephen P. Becker wrote: > >>The segfault with kernel oops that I can't get around occurs while >>glib's configure script is checking for libpthread. Specifically, it >>links http://beerandrocks.net:8080/~spbecker/oops/conftest.c against >>libpthread and then runs it. > > > If that oopses, your famed emerge testing hasn't run any threaded > programs, my friend :-) What do you mean by "famed" emerge testing? In any case, that is what I am in the process of doing (testing). This userland I am working with is in no way an official Gentoo install. :) At some point in the future, we will probably make official n32 install stages available to the general users, after we work all the bugs out...this just happens to be one of those bugs. > Could be kernel, could be library, could be both. Well, since you say that glibc 2.3.5 probably isn't up to par for mips64, I'll see if I can get cvs HEAD going in a chroot and see if that fixes the problem. > Must be at least kernel because the kernel should never oops. Agreed. -Steve From mboxrd@z Thu Jan 1 00:00:00 1970 From: "Bryan Althouse" Subject: RE: Seg fault when compiled with -mabi=64 and -lpthread Date: Fri, 1 Jul 2005 11:09:22 -0400 MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit In-Reply-To: <20050701035105.GA9601@nevyn.them.org> Message-ID: <20050701150938Z8226157-3678+821@linux-mips.org> Return-Path: Sender: linux-mips-bounce@linux-mips.org Errors-to: linux-mips-bounce@linux-mips.org To: 'Daniel Jacobowitz' , "'Stephen P. Becker'" , macro@blysk.ds.pg.gda.pl Cc: 'Linux/MIPS Development' Message-ID: <20050701150922.Vh7uF74pG6fj0aucwKfphfUvcYDZ8FBEWBQra1LcNkg@z> Thanks for everyone's input! Looks like I should upgrade glibc, and possibly gcc. When you say that I should try CVS HEAD of glibc, I'm not sure what you mean. I have looked in the linux-mips.org CVS and the closest thing I can find is libc, and it looks really old. I have also found a glibc CVS at :pserver:anoncvs@sources.redhat.com:/cvs/glibc. If I get libc from here is this the "CVS HEAD"? Should I get GCC from the generic GCC site, or should get it from the linux-mips CVS? I apologize for the simple questions. I have not built a tool chain before. I've been using the one supplied by PMC-Sierra. Will I need to patch any of these sources for MIPs? Bryan -----Original Message----- From: Daniel Jacobowitz [mailto:dan@debian.org] Sent: Thursday, June 30, 2005 11:51 PM To: Stephen P. Becker Cc: Ralf Baechle; Bryan Althouse; 'Linux/MIPS Development' Subject: Re: Seg fault when compiled with -mabi=64 and -lpthread On Thu, Jun 30, 2005 at 06:09:09PM -0400, Stephen P. Becker wrote: > > > 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? I don't think glibc 2.3.5 worked for mips64. But I haven't checked it in a long time. Try CVS HEAD of glibc instead. Other than that, you're on your own - building glibc is extremely error prone. -- Daniel Jacobowitz CodeSourcery, LLC