Problem reading corefiles on ARM

[Sergei Poselenov <sposelenov@emcraft.com>]

Hello,

I'm trying to test the GDB ability to analyze ARM coredumps:

-bash-3.2# gdb t core.967
GNU gdb Red Hat Linux (6.7-1rh)
Copyright (C) 2007 Free Software Foundation, Inc.
License GPLv3+: GNU GPL version 3 or later 
<http://gnu.org/licenses/gpl.html>
This is free software: you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law.  Type "show 
copying"
and "show warranty" for details.
This GDB was configured as "arm-linux"...
Using host libthread_db library "/lib/libthread_db.so.1".
Reading symbols from /lib/libc.so.6...done.
Loaded symbols for /lib/libc.so.6
Reading symbols from /lib/ld-linux.so.3...done.
Loaded symbols for /lib/ld-linux.so.3
Core was generated by `./t'.
Program terminated with signal 6, Aborted.
#0  0x4004ec0c in raise () from /lib/libc.so.6
(gdb) bt
#0  0x4004ec0c in raise () from /lib/libc.so.6
#1  0x40050234 in abort () from /lib/libc.so.6
Backtrace stopped: frame did not save the PC
(gdb) l
1       foo (int a, int b)
2       {
3               int c=40;
4               abort();
5               return a+b;
6       }
7       main()
8       {
9               printf("hello\n");
10              foo(10, 20);
(gdb)
11      }
(gdb)


My environment: ARM native GDB-6.7, toolchain is gcc-4.2.2,
binutils-2.17.50.0.12, glibc-2.6, built as cross-tools, 
arm-linux-eabi. Target running kernel 2.6.22.6.

Is this ARM GDB bug? I tried GDB 6.3 with non-eabi ARM toolchain
(gcc-4.0.0) running the same kernel - all the same.

Thanks for any help.

Regards,
Sergei