Re: How to properly run insight for eCos application?

[Gene Smith <gds@chartertn.net>]

Hello,
I don't know if I following everything you doing, but the "running man"
icon does not seem to do in insight what it does in most other
debuggers. Instead it means "reload your program" or something like
that. Once you see code on your screen you can set breakpoints and then
you must do the "continue" function: the ->{} icon or type C. When you
"continue" the running man changes to a STOP sign logo which you do
press to HALT your program. But to start up again, you do "continue".

Hope this helps.

-gene

ariga masahiro wrote:
> Hello everyone,
> 
> I do not know how to properly run insight for eCos application.
> Would you please teach me ?
> 
> I started to run insight like next on cygwin prompt.
> LINK@ariga ~/ether_test_plus_simplemain-O1
> $ sh-elf-insight.exe nc_test_slave.o
> 
> Then insight's source window appeared showing nc_test_slave.c.
> In order to break at sure point,I set breakpoint at top of cyg_start 
> function.
> Red square mark was shown.
> Then I clicked Running-Man icon,and DownLoading began and next log 
> appeared in console window.
> 
> 0x8000acb2 in ?? ()
> Loading section .text.cyg_start, size 0x2a0 lma 0x0
> Loading section .text.pexit, size 0x38 lma 0x0
> Loading section .rodata, size 0x3b0 lma 0x0
> Loading section .text.do_udp_test, size 0x65c lma 0x0
> Loading section .text.do_read, size 0xe0 lma 0x0
> Loading section .data.slave_tcp_port.3876, size 0x4 lma 0x0
> Loading section .text.do_tcp_test, size 0x620 lma 0x0
> Loading section .text.nc_slave, size 0x4f8 lma 0x0
> Loading section .text.net_test, size 0x68 lma 0x0
> Loading section .text.simple_program, size 0xdc lma 0x0
> Loading section .text.calibrate_load, size 0x50c lma 0x0
> Loading section .text.start_load, size 0x104 lma 0x0
> Loading section .text.net_load, size 0x9c lma 0x0
> Loading section .text.do_some_random_computation, size 0x78 lma 0x0
> Loading section .text.net_idle, size 0x4c lma 0x0
> Loading section .text.test_delay, size 0x38 lma 0x0
> Start address 0x0, load size 8652
> Transfer rate: 3 KB/sec, 298 bytes/write.
> (gdb)
> 
> When Download finished,"Make breakpoint pending on future shared library 
> load?" window poped up (why).
> I clicked "NO",then transfered to running state,Running-Man icon 
> changing to STOP icon,
> and down in Source Window "Program is running" appeared.
> But never breaked at breakpoint I would like to stop.
> I wonder where I was wrong?
> 
> I also tried to GDB remote debugging.
> Although it became nearly the same result,I appended log below.
> 
> --  this is GDB remote debugging log
> LINK@ariga ~/ether_test_plus_simplemain-O1
> $ sh-elf-gdb nc_test_slave.o
> GNU gdb 6.7.1
> 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 "--host=i686-pc-cygwin --target=sh-elf"...
> (gdb) set debug remote 1
> (gdb) set remotelogfile test-9.txt
> (gdb) set remotebaud 38400
> (gdb) target remote /dev/com2
> Remote debugging using /dev/com2
> Sending packet: $qSupported#37...Ack
> Packet received:
> Packet qSupported (supported-packets) is NOT supported
> Sending packet: $Hc-1#09...Ack
> Packet received: OK
> Sending packet: $qC#b4...Ack
> Packet received: E02
> Sending packet: $qOffsets#4b...Ack
> Packet received:
> Sending packet: $?#3f...Ack
> Packet received: S05
> Sending packet: $Hg0#df...Ack
> Packet received: OK
> Sending packet: $g#67...Ack
> Packet received: 
> 40000101ffffff0f40000101400001f18000aca400000005000000060000000
> 700000008000000090000000a0000000b0000000c0000000d8ffecf948ffecf948000acb28000cf0 
> 
> e42df3e8480000000000000000000000040000101000000000000000000000000000000000000000 
> 
> 00000000000000000000000000000000000000000000000000000000000000000000000000000000 
> 
> 0000000000000000000000000000000000000000040000101ffffff0f40000101400001f18000aca 
> 
> 40000000500000006000000070000000000000000000000000000000000000000000000000000000 
> 
> 000000000
> 0x8000acb2 in ?? ()
> Sending packet: $qSymbol::#5b...Ack
> Packet received:
> Packet qSymbol (symbol-lookup) is NOT supported
> (gdb) b cyg_start
> Breakpoint 1 at 0x1f38: file nc_test_slave.c, line 721.    --- 
> breakpoint was set.
> (gdb)
> (gdb)load
>  |
> here appeared lot of binary code.
>  |
> Loading section .text.test_delay, size 0x38 lma 0x0
> Sending packet: $X0,38:/覦"\177・�eR%H\021Og縢トR\177畚0001'3:R\177a3d 
> \023e}\003ム
> \004A\013\000\t~\004o絨&n�000\013\000\t\000\000\000\000#3c...Ack
> Packet received: OK
> Start address 0x0, load size 8652
> Sending packet: $P10=00000000#6e...Ack
> Packet received: OK
> Packet P (set-register) is supported
> Transfer rate: 2 KB/sec, 298 bytes/write.
> (gdb) c
> Continuing.
> Sending packet: $Z0,1f38,2#16...Ack
> Packet received:
> Packet Z0 (software-breakpoint) is NOT supported
> Sending packet: $m1f38,2#cd...Ack
> Packet received: 5232
> Sending packet: $X1f38,2:テ #d5...Ack
> Packet received: OK
> Sending packet: $vCont?#49...Ack
> Packet received:
> Packet vCont (verbose-resume) is NOT supported
> Sending packet: $Hc0#db...Ack
> Packet received: OK
> Sending packet: $c#63...Ack
> 
> Like insight it never breaked.
> 
> I append test-9.txt logfile compressed in gzip file.
> 
> Especially I have next suspicious points.
> 1.Am I correct using nc_test_slave.o in starting dubugger ?
> 2.There is other way to run program, so surely break at cyg_start().
> 
> Please help me.
> Thank you in advance.
> 
> Masahiro Ariga