This is the mail archive of the mailing list for the Insight project.

Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

Re: Problem with Remote/Serial in Insight

On Tue, 2004-12-14 at 13:08, Bernhard Walle wrote:

> What do you mean with "whole session"? Just break main and target 
> remote, or am I understanding wrong?

I would like to see something like this but targeted for your stub:

$ ./gdb -q -nx
(gdb) file ~/pi/pi-print.arm-elf
Reading symbols from /home/keiths/pi/pi-print.arm-elf...done.
(gdb) b main
Breakpoint 1 at 0x80fc: file pi.c, line 25.
(gdb) tar sim
Connected to the simulator.
(gdb) load
Loading section .text, size 0x9210 vma 0x8000
Loading section .rodata, size 0x314 vma 0x11210
Loading section .data, size 0x864 vma 0x11624
Loading section .ctors, size 0x8 vma 0x11e88
Loading section .dtors, size 0x8 vma 0x11e90
Start address 0x8000
Transfer rate: 322752 bits in <1 sec.
(gdb) r
Starting program: /home/keiths/pi/pi-print.arm-elf
Breakpoint 1, main (argc=1, argv=0x1ffffc) at pi.c:25
25            int i=0;

I would like to see the series of commands that you use to start your
debugging. There is a disconnect between the way you and your stub works
and the way Insight does. By understanding exactly how your target
starts, I can get a better understanding of what insight should be doing
in your case.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]