problem reading /proc/net/route on amd64

[agriffis]

Configuration Information [Automatically generated, do not change]:
Machine: x86_64
OS: linux-gnu
Compiler: x86_64-pc-linux-gnu-gcc
Compilation CFLAGS:  -DPROGRAM='bash' -DCONF_HOSTTYPE='x86_64' 
-DCONF_OSTYPE='linux-gnu' -DCONF_MACHTYPE='x86_64-pc-linux-gnu' 
-DCONF_VENDOR='pc' -DLOCALEDIR='/usr/share/locale' -DPACKAGE='bash' -DSHELL 
-DHAVE_CONFIG_H  -I.  -I. -I./include -I./lib   -O0 -ggdb -pipe
uname output: Linux olive 2.6.11-gentoo-r4 #4 Mon May 16 10:19:39 EDT 2005 
x86_64 AMD Athlon(tm) 64 Processor 3200+ AuthenticAMD GNU/Linux
Machine Type: x86_64-pc-linux-gnu

Bash Version: 3.0
Patch Level: 16
Release Status: release

Description:
        bash stops after the first line when using bash internals to read
        /proc/net/route on amd64.  I've verified this on both Gentoo and Debian,
        both running bash-3.0-16.  I've also tested with the same version of
        bash on alpha, ia64 and x86 and verified that it doesn't happen there.

Repeat-By:
$ echo "$(</proc/net/route)"
Iface   Destination     Gateway         Flags   RefCnt  Use     Metric  Mask    
        MTU     Window  IRTT                                                    
   
$ cat /proc/net/route
Iface   Destination     Gateway         Flags   RefCnt  Use     Metric  Mask    
        MTU     Window  IRTT                                                    
   
eth0    0000000A        00000000        0001    0       0       0       
0000FFFF        0       0       0                                               
                                
lo      0000007F        00000000        0001    0       0       0       
000000FF        0       0       0                                               
                                  
eth0    00000000        0600000A        0003    0       0       0       
00000000        0       0       0                                               
                                

Fix:
        I'm continuing to debug this problem, since it's hard to believe that
        it's really the fault of bash, but raising it early in hopes of getting
        some help...