> With both this and bin/8461, seems like a very strong case to turn off
> HAVE_MMAP.  Any objections?

Gah, even doing that appears not to be sufficient to cure the
problem:

vever# cd /sys/arch/i386
vever# find . -type f | xargs egrep XXBLAHXX
egrep: memory exhausted
egrep: memory exhausted
vever# find . -type f -size +4000 -ls
 122221   6400 -rwxr-xr-x    1 root     wheel      3264606 Oct 25 14:24 ./compile/GENERIC/netbsd
 800446   6752 -rwxr-xr-x    1 root     wheel      3445282 Jul 15 16:57 ./compile/INSTALL/netbsd
  42399   4960 -rwxr-xr-x    1 root     wheel      2524794 Jul 15 17:02 ./compile/INSTALL_TINY/netbsd
 929336  43792 -rwxr-xr-x    1 root     wheel     22395758 Oct 25 19:31 ./compile/SERVER/netbsd.gdb
 532948   6320 -rwxr-xr-x    1 root     wheel      3223473 Oct 25 11:05 ./compile/SERVER_1/netbsd
 532947  72608 -rwxr-xr-x    1 root     wheel     37136160 Oct 25 11:05 ./compile/SERVER_1/netbsd.gdb
 457225  44928 -rwxr-xr-x    1 root     wheel     22976155 Oct 25 18:46 ./compile/SERVER_2/netbsd.gdb
  56770  43504 -rwxr-xr-x    1 root     wheel     22241975 Oct 25 14:41 ./compile/RYPE/netbsd.gdb
vever# limit
cputime         unlimited
filesize        unlimited
datasize        131072 kbytes
stacksize       2048 kbytes
coredumpsize    unlimited
memoryuse       57984 kbytes
memorylocked    19328 kbytes
maxproc         532 
openfiles       64 
vever#

- Havard