From: hilbert via Gdb <gdb@sourceware.org>
To: "Luis Machado" <luis.machado@arm.com>
Cc: gdb@sourceware.org
Subject: Re:Re: How does GDB get the function call stack
Date: Tue, 16 Aug 2022 17:19:16 +0800 (CST) [thread overview]
Message-ID: <5c30085e.8da0.182a5f3377d.Coremail.swdtian@163.com> (raw)
In-Reply-To: <217b746f-65e8-66c0-1678-376eb8cb1aca@arm.com>
@Luis Machado
Thank you very much .
What does the sentence “functions without debug information”mean? Does it refer to the call stack information from the rpb register?
If there is no debug information, the call stack can be obtained. Why does gdb still need DWARF2 unwind information?
At 2022-08-16 15:56:52, "Luis Machado" <luis.machado@arm.com> wrote:
>On 8/16/22 08:43, hilbert via Gdb wrote:
>> Hi ,
>> There are 4 ways to get the function call stack in the GDB Internals Manual. https://sourceware.org/gdb/papers/unwind.html
>> For x86_64, does GDB get information by parsing the .eh_frame section? Or just get the call stack by Parse the function prologues.
>>
>>
>>
>
>I'd say mostly 1 and 2. 1 is usually used with functions without debug information. 2 is used when there is debug information.
next prev parent reply other threads:[~2022-08-16 9:20 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-08-16 7:43 hilbert via Gdb
2022-08-16 7:56 ` Luis Machado via Gdb
2022-08-16 9:19 ` hilbert via Gdb [this message]
2022-08-16 9:33 ` Andrew Dinn via Gdb
2022-08-16 10:16 ` hilbert via Gdb
2022-08-16 12:48 ` Andrew Dinn via Gdb
2022-08-16 13:18 ` hilbert via Gdb
2022-08-16 13:27 ` Luis Machado via Gdb
2022-08-16 13:46 ` hilbert via Gdb
2022-08-18 14:05 ` Andrew Burgess via Gdb
2022-08-19 1:57 ` hilbert via Gdb
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=5c30085e.8da0.182a5f3377d.Coremail.swdtian@163.com \
--to=gdb@sourceware.org \
--cc=luis.machado@arm.com \
--cc=swdtian@163.com \
/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