Hi,
I'm trying to setup a kernel debugging environment for the Gumstix Overo
Earth (TI OMAP 3503) + Palo43 using Eclipse.
I have enabled kgdb in the kernel (linux-omap-2.6.32 based android kernel).
My bootargs were
# setenv console ttyS2,115200n8
# setenv mmcargs 'setenv bootargs console=${console} vram=12M omapfb.vram=0:4M
omapfb.mode=dvi:${dvimode} omapdss.def_disp=${defaultdisplay}
root=/dev/mmcblk0p2 rw rootfstype=ext3 rootwait init=/init kgdboc=${console}
kgdbwait'
The kernel boots and waits correctly for input as follows:
console [ttyS2] enabled
kgdb: Registered I/O driver kgdboc.
kgdb: Waiting for connection from remote gdb...
I have also configure Eclipse IDE, and built the kernel, and when I run it in
debug mode, it launches the kernel and the whole android OS boots correctly,
and Eclipse IDE shows a number of threads running, but I can seem to see any
source code highlighted, even through I set a breakpoint in board-overo.c (my
board file) for the init board routine. It should have stopped and paused
execution at the breakpoint.
Question 01: When building from Eclipse IDE, it builds uImage, but for the
debug settings, I selected vmlinux that was generated in the root folder. I ran
uImage on the target board, but for the executable for the debug session I used
vmimage. Is that correct?
When I launch Eclipse debugger, I can see a number of threads running, it
doesn't display any source code, I can't pause any threads, and the breakpoints
don't appear to be working.
What should I do ?
Best regards,
Elvis Dowson
--
To unsubscribe from this list: send the line "unsubscribe linux-omap" in
the body of a message to [email protected]
More majordomo info at http://vger.kernel.org/majordomo-info.html
