Subject: A gcc process that gets "stuck"?
To: None <email@example.com>
From: Lars Nordlund <firstname.lastname@example.org>
Date: 12/21/2004 02:44:37
I am investigating a strange phenomena on an alpha:
NetBSD 2.0 (GENERIC) #0: Tue Nov 30 21:04:03 UTC 2004
Digital AlphaPC 164SX 533 MHz, s/n
8192 byte page size, 1 processor.
total memory = 320 MB
(2128 KB reserved for PROM, 317 MB used by NetBSD)
The installation works fine. I suppose. I was a bit surprised to find
that I had to edit rc.conf to get to multiuser (together with the 'A'
boot flag added as a boot argument) but I suspect that is how it is
supposed to work.. I had expected it to remember network settings (don't
think it did) like on the i386, but anyway.. That was no big problems
Trying to run a compiler on the machine just fails. Nothing happens. The
process gets stuck.
$ cat testa.c
$ gcc -o testa testa.c
Nothing more happens here. The CPU is running 100% chewing on this small
C file, but never reaches a conclusion.
$ ktruss gcc -o testa testa.c
859 ktruss emul(netbsd)
859 ktruss execve("/home/lars/bin/gcc", 0x1fffff700, 0x1fffff728)
859 ktruss execve("/bin/gcc", 0x1fffff700, 0x1fffff728) Err#2
350 gcc close(0x3) = 0
350 gcc __stat13("/usr/bin/../libexec/cc1", 0x1ffffeaf8) = 0
350 gcc access("/usr/bin/../libexec/cc1", 0x1) = 0
350 gcc fork() = 767
It can't fork()?