ARM/linux gdb stops and gives no info

[Richard Earnshaw <rearnsha at arm dot com>]

Using the gdb-5.0 rpm from ftp://ftp.netwinder.org/users/s/scottb/current/g
db-5.0-1nw1.armv4l.rpm
(which I believe is a straight build of the gdb-5.0 sources for the 
netwinder),  I hit the following problem while trying to debug cc1plus on 
a Netwinder box.

$ gdb cc1plus
GNU gdb 5.0 (UI_OUT)
Copyright 2000 Free Software Foundation, Inc.
GDB is free software, covered by the GNU General Public License, and you 
are
welcome to change it and/or distribute copies of it under certain 
conditions.
Type "show copying" to see the conditions.
There is absolutely no warranty for GDB.  Type "show warranty" for details.
This GDB was configured as "armv4l-unknown-linux-gnu"...
Breakpoint 1 at 0x2001278
Breakpoint 2 at 0x20711d0: file /net/home/rearnsha/gnusrc/egcs/gcc/rtl.c, 
line 1261.
Breakpoint 3 at 0x2001048
(gdb) run -O2 -fPIC t.i
Starting program: /home/rearnsha/gnu/egcs/gcc/cc1plus -O2 -fPIC t.i
Breakpoint 1 at 0x4004947c: file exit.c, line 40.
Breakpoint 3 at 0x40048110: file ../sysdeps/generic/abort.c, line 55.
During symbol reading...register number 258 too large (max 26) in symbol 
buf...
type_info::~type_info ()bool type_info::operator== (const type_info &) 
constvoid __rtti_class (void *, const char *, const 
__class_type_info::base_info *, unsigned int)void __rtti_si (void *, const 
char *, const type_info *)void __rtti_user (void *, const char *)int 
__user_type_info::upcast (const type_info &, void *, void **) constvoid 
*__user_type_info::dyncast (int, const type_info &, void *, const 
type_info &, void *) const
Program received signal SIGSEGV, Segmentation fault.
Cannot access memory at address 0x0
(gdb) where
Cannot access memory at address 0x0
(gdb) info reg 
No selected frame.
(gdb) 

There seems to be nothing I can do to get gdb to tell me what happened.

I get the same problem with a gdb I've built direct from the sources 
(though I had some local mods in that code)...

I can understand not being able to unpick the stack frame if I've jumped 
to never-never land, but to not even be able to display the registers 
makes the debugger useless.

R.