From: Ahmad Nouralizadeh <ahmad.mlists@gmail.com>
To: Jan Kratochvil <jan.kratochvil@redhat.com>
Cc: "gdb@sourceware.org" <gdb@sourceware.org>
Subject: Re: GDB Frame Unwinding for Pure Assembly Code
Date: Tue, 23 Jun 2020 16:18:42 +0430 [thread overview]
Message-ID: <CAMYFX7nxegE8ZZKGT3JQMS3B7kxf9BErn+sWxYknkxpej-cvew@mail.gmail.com> (raw)
In-Reply-To: <20200623072654.GA3548953@host1.jankratochvil.net>
Hi Jan,
Thanks for the answer! Could you tell me why is an inline unwinder used?
Regards.
On Tuesday, 23 June 2020, Jan Kratochvil <jan.kratochvil@redhat.com> wrote:
> On Mon, 22 Jun 2020 23:55:30 +0200, Ahmad Nouralizadeh via Gdb wrote:
> > But knowing the GDB mechanism to get over the problem will be helpful.
>
> GDB disassembles the code and tries to guess how to unwind it.
> amd64-tdep.c amd64_analyze_prologue(), amd64_frame_cache_1() etc.
>
> That is just a last resort way of unwinding (=a bug in the debuggee), there
> should always be .eh_frame in the debuggee, also for throwing exceptions
> across such .eh_frame-less functions if there is any callback there.
>
>
> Jan
>
>
next prev parent reply other threads:[~2020-06-23 11:48 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-06-22 21:29 Ahmad Nouralizadeh
2020-06-22 21:39 ` Jan Kratochvil
2020-06-22 21:55 ` Ahmad Nouralizadeh
2020-06-23 7:26 ` Jan Kratochvil
2020-06-23 11:48 ` Ahmad Nouralizadeh [this message]
2020-06-23 12:23 ` Jan Kratochvil
2020-06-23 14:23 ` Ahmad Nouralizadeh
2020-06-24 14:00 ` Simon Marchi
2020-06-24 19:09 ` Ahmad Nouralizadeh
2020-06-24 15:06 ` Andrew Burgess
2020-06-25 9:10 ` Ahmad Nouralizadeh
2020-06-25 16:51 ` Andrew Burgess
2020-06-26 11:33 ` Ahmad Nouralizadeh
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=CAMYFX7nxegE8ZZKGT3JQMS3B7kxf9BErn+sWxYknkxpej-cvew@mail.gmail.com \
--to=ahmad.mlists@gmail.com \
--cc=gdb@sourceware.org \
--cc=jan.kratochvil@redhat.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).