> /usr/local/netbsd-tools/current/bin/arm--netbsdelf-gcc -Os  -Wall 
> -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith 
> -Wno-sign-compare -Wno-traditional -Wno-uninitialized -Wreturn-type 
> -Wswitch -Wshadow  -Werror   -DBACKWARDS -DDES  -nostdinc -isystem 
> /u1/diskless/shark/usr/include  -c    /u1/netbsd/src/bin/ed/buf.c
> arm--netbsdelf-gcc: Internal error: Cputime limit exceeded (program cc1)
> Please submit a full bug report.
> See <URL:http://gcc.gnu.org/bugs.html> for instructions.
> 
> *** Failed target:  buf.o
> *** Failed command: 
> /usr/local/netbsd-tools/current/bin/arm--netbsdelf-gcc -Os -Wall 
> -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith 
> -Wno-sign-compare -Wno-traditional -Wno-uninitialized -Wreturn-type 
> -Wswitch -Wshadow -Werror -DBACKWARDS -DDES -nostdinc -isystem 
> /u1/diskless/shark/usr/include -c /u1/netbsd/src/bin/ed/buf.c
> 
> Anyone else had this problem?

Nope.  Maybe it's related to the new signal code?  Delivering the wrong 
signal somehow?

> 
> yeah-baby:thorpej 199$ ulimit -a
> time(cpu-seconds)    unlimited
> file(blocks)         unlimited
> coredump(blocks)     unlimited
> data(kbytes)         1048576
> stack(kbytes)        2048
> lockedmem(kbytes)    169298
> memory(kbytes)       507896
> nofiles(descriptors) 512
> processes            160
> yeah-baby:thorpej 200$
> 
> I'm a little confused as to why it happens!
> 
>          -- Jason R. Thorpe <thorpej@wasabisystems.com>
>