Re: [ECOS] GDB Download on i386 target hangs

[Christian Plessl <cplessl at ee dot ethz dot ch>]

>What program are you actually running? Do any of the standard test
>programs run? Do not take too much notice of what GDB says the
>location is here. It is confused by the address being outside it's
>known range and is making a guess.
>
>Try "x/1i 0x3270". On my machine this gives
>
>0x3270: fild   (%edx)
>
>which looks like it is halfway through an instruction in the stub
>monitor.

Unfortunately, I still have troubles downlaoding.
I tried to run many kernel tests, but there is always the same problem.

I captured my attempt to run the tm_basicthe test:

I configured ecos in a new directory, using the commands

ecosconfig new pc
ecosconfig check
ecosconfig tree
make
make tests

then, chdir to the install/kernel/test directory ..


[cplessl@pluto tests]$ i386-elf-gdb -nw tm_basic
GNU gdb 5.0
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 "--host=i686-pc-linux-gnu --target=i386-elf"...

(gdb) target remote /dev/ttyS0
Remote debugging using /dev/ttyS0
0x334e in ?? ()
     at 
/usr/local/pack/ecos-cvs/ecos/packages/services/memalloc/common/current/src/dlmalloc.cxx:1257
1257      return chunk2mem(victim);

(gdb) load
Loading section .text, size 0xc118 lma 0x10000
Loading section .rodata, size 0xdfd lma 0x1c118
Loading section .data, size 0x288 lma 0x1cf18
Start address 0x10000 , load size 53661
Transfer rate: 20442 bits/sec, 76 bytes/write.

(gdb) continue
Continuing.
Program received signal SIGILL, Illegal instruction.
0x3273 in ?? ()
     at 
/usr/local/pack/ecos-cvs/ecos/packages/services/memalloc/common/current/src/dlmalloc.cxx:1257
1257      return chunk2mem(victim);

(gdb) x/1i 0x3273
0x3273: (bad)


As you see, It seems as if at location 0x3273 was no valid instruction..

Does anybody have an idea how to solve this problem?


--
Christian Plessl, Loorenstr. 20, 5443 Niederrohrdorf
Tel, Fax: 056 496 41 73    email: cplessl@ee.ethz.ch