SCORE gdb run testsuite dump.exp fail, why?

ligang
2008-01-04T09:25:53Z

Hello all,

SCORE gdb run testsuite dump.exp fail by little endian, whereas big endian
is correct.
Maybe the memory is not correct after "file intarr1.srec"

The following is gdb running context:
(gdb) dump srec val intarr1.srec intarray
(gdb) file intarr1.srec
(gdb) x/32w intarray
0xb20 <intarray>: 0x01000000 0x02000000 0x03000000
0x04000000
0xb30 <intarray+16>: 0x05000000 0x06000000 0x07000000
0x08000000
0xb40 <intarray+32>: 0x09000000 0x0a000000 0x0b000000
0x0c000000
0xb50 <intarray+48>: 0x0d000000 0x0e000000 0x0f000000
0x10000000
0xb60 <intarray+64>: 0x11000000 0x12000000 0x13000000
0x14000000
0xb70 <intarray+80>: 0x15000000 0x16000000 0x17000000
0x18000000
0xb80 <intarray+96>: 0x19000000 0x1a000000 0x1b000000
0x1c000000
0xb90 <intarray+112>: 0x1d000000 0x1e000000 0x1f000000
0x20000000

The content of intarr1.srec is below:
S00F0000696E74617272312E7372656354
S1130B2001000000020000000300000004000000B7
S1130B300500000006000000070000000800000097
S1130B40090000000A0000000B0000000C00000077
S1130B500D0000000E0000000F0000001000000057
S1130B601100000012000000130000001400000037
S1130B701500000016000000170000001800000017
S1130B80190000001A0000001B0000001C000000F7
S1130B901D0000001E0000001F00000020000000D7
S9030000FC

Is the intarr1.srec error or the memory is error after execute "file
intarr1.srec"?
Which hook can resolve this problem?
Thanks.

Ligang