gdb cross debugging with core files: no backtrace and no sharedlibrary loading

[crquan <crquan at gmail dot com>]

Hi all,

I have been using gdb-7.3 for my arm linux board projects for a long time,
for most applications memory crash problems I debug the program with a
core file under gdb, with correct sysroot and solib-search-path, the
backtrace command
was always able to indicate where it crashed,
but with a recent ported program, it ceased working, no any symbol
from sharedlibrary loaded, and backtrace just gave addresses with no
symbol,
that I cannot guess at that address is it a function, from binary text
or a library text section?

I'm not sure is this a gdb bug or I used it wrong, I compiled a
gdb-7.6 but got same; want to see if any one met same or similar
error, and how can I manually load symbol table from those libraries?
any suggests or comments are welcome,
Thanks,


(gdb) bt 10
#0  0x402f6040 in ?? ()
#1  0x402f6030 in ?? ()
#2  0x402f6030 in ?? ()
Backtrace stopped: previous frame identical to this frame (corrupt stack?)
(gdb) info sharedlibrary
No shared libraries loaded at this time.
(gdb) info symbol 0x402f6040
No symbol matches 0x402f6040.


(gdb) show version
GNU gdb (GDB) 7.6
Copyright (C) 2013 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=x86_64-unknown-linux-gnu
--target=arm-unknown-linux-gnu".
For bug reporting instructions, please see:
<http://www.gnu.org/software/gdb/bugs/>.

(gdb) show sysroot
[...]
(gdb) show solib-search-path
[...]