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 21:46:17 +0800 (CST) [thread overview]
Message-ID: <7d4c1a29.7df1.182a6e7ad60.Coremail.swdtian@163.com> (raw)
In-Reply-To: <b0533570-6705-e841-47ca-06168c048956@arm.com>
>Sorry, for some funny reason (mailing list software/mail server) I'm not getting hilbert's replies. But Andrew provided great answers.
>Reading memory is usually done through /proc/<pid>/mem these days, as it is fastest.
>
>Reading registers for each thread is done by ptrace.
>
> regards,
>
> Andrew Dinn
I totally get it . This is very helpful for me.
Thanks.
next prev parent reply other threads:[~2022-08-16 13:47 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
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 [this message]
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=7d4c1a29.7df1.182a6e7ad60.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