[ECOS] RE: ctrl-c in GDB

Nick Garnett nickg@ecoscentric.com
Tue Sep 28 21:05:00 GMT 2004


"Vikas K. Prasad" <vikas.prasad@ittiam.com> writes:

> Hi,
> 
> I got the interrupt to work. The UART RSR register
> was not  read  (and so the interrupt bit was never
> cleared).
> 
> However, I am still having issues with gdb ^c. Can
> someone help me out? The program is loaded correctly
> but control does not get transfered to application
> and neither the ^c work.
> 
> (gdb) so ldl.spt
> 0x00003018 in ?? ()
> Loading section .rom_vectors, size 0x40 lma 0x4100000
> Loading section .text, size 0xf6c8 lma 0x4100180
> Loading section .rodata, size 0x26c lma 0x410f848
> Loading section .data, size 0x3a0 lma 0x410fab4
> Start address 0x4100180, load size 64788
> Transfer rate: 86384 bits/sec, 298 bytes/write.
> (gdb) c
> Continuing.
> Interrupted while waiting for the program.
> Give up (and stop debugging it)? (y or n) y

If the program just dies without giving any output, then the best
thing to do is to plant some breakpoints in the startup code and find
how far it gets. A bit of binary chopping will narrow the area where
it is failing down and you should be able to find out where it fails.

Also try running some of the standard kernel tests provided with
eCos. If these fail then there is something wrong with the board
port.

-- 
Nick Garnett                    eCos Kernel Architect
http://www.ecoscentric.com/     The eCos and RedBoot experts


-- 
Before posting, please read the FAQ: http://ecos.sourceware.org/fom/ecos
and search the list archive: http://ecos.sourceware.org/ml/ecos-discuss



More information about the Ecos-discuss mailing list