public inbox for gdb@sourceware.org
 help / color / mirror / Atom feed
From: Luis Machado <luis.machado@arm.com>
To: hilbert <swdtian@163.com>, gdb@sourceware.org
Subject: Re: How does GDB get the function call stack
Date: Tue, 16 Aug 2022 08:56:52 +0100	[thread overview]
Message-ID: <217b746f-65e8-66c0-1678-376eb8cb1aca@arm.com> (raw)
In-Reply-To: <700833f8.5150.182a59bc271.Coremail.swdtian@163.com>

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.

  reply	other threads:[~2022-08-16  7:57 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-08-16  7:43 hilbert
2022-08-16  7:56 ` Luis Machado [this message]
2022-08-16  9:19   ` hilbert
2022-08-16  9:33     ` Andrew Dinn
2022-08-16 10:16       ` hilbert
2022-08-16 12:48         ` Andrew Dinn
2022-08-16 13:18           ` hilbert
2022-08-16 13:27           ` Luis Machado
2022-08-16 13:46             ` hilbert
2022-08-18 14:05   ` Andrew Burgess
2022-08-19  1:57     ` hilbert

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=217b746f-65e8-66c0-1678-376eb8cb1aca@arm.com \
    --to=luis.machado@arm.com \
    --cc=gdb@sourceware.org \
    --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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).