From: SUN Michael <evcode@outlook.com>
To: "gdb@sourceware.org" <gdb@sourceware.org>
Subject: [gdb v10] My Build Cannot Tell the Symbol Info. to Debug the Core Dump
Date: Mon, 26 Jul 2021 10:40:12 +0000 [thread overview]
Message-ID: <SYBPR01MB5791D8D7F6D3DB07D05DEB98C2E89@SYBPR01MB5791.ausprd01.prod.outlook.com> (raw)
Hi team,
Now I meet an issue when to debug the core dump file. That’s it:
Using gdb v9 and the older version the related symbol files will be auto loaded following the command:
$ gdb $EXE $CORE -ex “set sysroot $SYMBOL_PATH”
GNU gdb (GDB) 9.2
Copyright (C) 2020 Free Software Foundation, Inc.
… …
Reading symbols from <$EXE>...
[New LWP 1800]
[New LWP … ]
… …
Reading symbols from XXX
… …
(gdb)
However, on gdb v10 there’s no “Reading symbols from” processing:(,
and the console directly goes to “(gdb)” without any wait or prompt.
And then after I typed “bt”, there’ no symbol information ― it seems the symbols have not been loaded at all:
#0 0x0000000c0d8b50 in ?? ()
#1 0x0000000ddbd808 in ?? ()
I CROSS-compiled v9 and v10 using the same configuration as below:
configure --host=x86_64-pc-linux-gnu --target=aarch64-linux-android --with-python=/usr/bin/python --with-expat --with-lzma
, and my v10’s “show configuration”:
configure --host=x86_64-pc-linux-gnu --target=aarch64-linux-android
--with-auto-load-dir=$debugdir:$datadir/auto-load
--with-auto-load-safe-path=$debugdir:$datadir/auto-load
--with-expat
--with-gdb-datadir=/XXX/gdb/gdb-10/share/gdb (relocatable)
--with-jit-reader-dir=/XXX/gdb/gdb-10/lib/gdb (relocatable)
--without-libunwind-ia64
--with-lzma
--without-babeltrace
--without-intel-pt
--without-mpfr
--without-xxhash
--with-python=/usr
--with-python-libdir=/usr/lib
--without-debuginfod
--without-guile
--disable-source-highlight
--with-separate-debug-dir=/XXX/gdb/gdb-10/lib/debug (relocatable)
Appreciate for your attention and help in advance:)
THX!!
Best regards,
Michael SUN
next reply other threads:[~2021-07-26 10:40 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-07-26 10:40 SUN Michael [this message]
2021-07-26 12:52 ` Andrew Burgess
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=SYBPR01MB5791D8D7F6D3DB07D05DEB98C2E89@SYBPR01MB5791.ausprd01.prod.outlook.com \
--to=evcode@outlook.com \
--cc=gdb@sourceware.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).