From: Jaap-Jan <jjboor@lucent.com>
To: linuxppc-embedded@lists.linuxppc.org
Subject: occasionally segmentation faults
Date: Wed, 31 Jul 2002 12:28:38 +0200 (MEST) [thread overview]
Message-ID: <200207311028.MAA25657@hzsms01.nl.lucent.com> (raw)
Hi,
I've some problems with my built cross environment
from sparc-solaris to powerpc 8xx.
I configured and built gcc2.95.2 and glibc-2.1.3
and used that to build the file and sh utils etc.
I applied the cache line size patch, removed sysdeps/powerpc/memset.S
and used this config command for glibc:
CC=powerpc-linux-gcc AR=powerpc-linux-ar RANLIB=powerpc-linux-ranlib
CFLAGS="-mcpu=860 -msoft-float -O2 -DNDEBUG=1"
../../src-nfp/glibc-2.1.3/configure --host=powerpc-linux
--with-headers=$HOME/linux/include --enable-add-ons=crypt,linuxthreads
--enable-shared --without-fp --prefix=$HOME/crosstools/target/powerpc-linux-gnu
All seems to work initially on our target, however sometimes
I get a segmentation fault. E.g. I can run 5 times 'ls', then
suddenly the 6th time I get a seg. fault, the 7th time I get
this error from bash: 'child setpgid (266 to 265): Operation not permitted'
I also cross-compiled ldconfig and ran it on target to create a ld.so.cache
but that doesn;t help
eg:
bash-2.04# ls
bin etc lib linuxrc mnt root tmp
dev home libexec lost+found proc sbin usr
bash-2.04# ls
Segmentation fault
bash-2.04# ls
bash: child setpgid (266 to 265): Operation not permitted
bin etc lib linuxrc mnt root tmp
dev home libexec lost+found proc sbin usr
bash-2.04# cat /proc/ppc_htab
Non-error misses: 67059
Error misses : 44
Anyone an idea?
thanks,
Jaap-Jan
** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/
next reply other threads:[~2002-07-31 10:28 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-07-31 10:28 Jaap-Jan [this message]
2002-07-31 11:18 ` occasionally segmentation faults Wolfgang Denk
-- strict thread matches above, loose matches on Subject: below --
2002-08-08 13:45 Jaap-Jan Boor
2002-08-08 20:12 ` Wolfgang Denk
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=200207311028.MAA25657@hzsms01.nl.lucent.com \
--to=jjboor@lucent.com \
--cc=linuxppc-embedded@lists.linuxppc.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 NNTP newsgroup(s).