On Tue, Aug 12, 2014 at 05:30:03AM +0200, Patrick Georgi wrote:
Am 12.08.2014 um 00:37 schrieb Piotr Król:
Anyone know how to load bootblock debug symbols to gdb when debugging using '-s -S' option ?
add-symbol-file $filename $loadaddr
When I try:
gdb$ target remote :1234 Remote debugging using :1234 gdb$ add-symbol-file build/cbfs/fallback/bootblock.debug 0x0 add symbol table from file "build/cbfs/fallback/bootblock.debug" at .text_addr = 0x0 Reading symbols from /home/pietrushnic/src/coreboot/build/cbfs/fallback/bootblock.debug...warning: section .text not found in /home/pietrushnic/src/coreboot/build/cbfs/fallback/bootblock.debug done.
Same thing for romstage.debug. When using ramstage without address:
gdb$ add-symbol-file build/cbfs/fallback/ramstage.debug The address where build/cbfs/fallback/ramstage.debug has been loaded is missing
And with address: gdb$ add-symboadd-symbol-file build/cbfs/fallback/ramstage.debug 0x0 add symbol table from file "build/cbfs/fallback/ramstage.debug" at .text_addr = 0x0 Reading symbols from /home/pietrushnic/src/coreboot/build/cbfs/fallback/ramstage.debug...done.
But util/crossgcc/xgcc/bin/armv7-a-eabi-gdb doesn't break on methods and does not show executed line of code. Symbols seems to be loaded but I cannot use them to debug. Any ideas how to debug qemu system using armv7-a-eabi-gdb ?
Thanks, Piotr