While debugging u-boot by BDI3000 and GDB, I have the following issue. Do you encounter such a problem? How to fix it? Any suggestions are warmly welcome?
(gbd) n [wangsy@localhost u-boot]$ /home/wangsy/gdb-mips/bin/mips-linux-gdb u-boot-octeon_bbgw_ref_failsafe GNU gdb (GDB) 7.2 Copyright (C) 2010 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-linux-gnu --target=mips-linux". For bug reporting instructions, please see: http://www.gnu.org/software/gdb/bugs/... Reading symbols from /home/wangsy/uboot_porting/OCTEON-SDK_1008_ago/bootloader/u-boot/u-boot-octe on_bbgw_ref_failsafe...done. (gdb) target extended-remote 192.168.5.20:2001 Remote debugging using 192.168.5.20:2001 0x1fc0003c in ?? () (gdb) n warning: GDB can't find the start of the function at 0x1fc0003c.
GDB is unable to find the start of the function at 0x1fc0003c and thus can't determine the size of that function's stack frame. This means that GDB may be unable to access that stack frame, or the frames below it. This problem is most likely caused by an invalid program counter or stack pointer. However, if you think GDB should simply search farther back from 0x1fc0003c for code which looks like the beginning of a function, you can increase the range of the search using the `set heuristic-fence-post' command. Cannot find bounds of current function (gdb) set heuristic-fence-post 0 (gdb) n warning: GDB can't find the start of the function at 0x1fc0003c. Cannot find bounds of current function (gdb) n Cannot find bounds of current function (gdb) n Cannot find bounds of current function
Thanks! Shuyou