From: Eli Zaretskii <eliz@gnu.org>
To: Abdul Basit Ijaz <abdul.b.ijaz@intel.com>
Cc: gdb-patches@sourceware.org, abdul.b.ijaz@intel.com,
JiniSusan.George@amd.com, tom@tromey.com, blarsen@redhat.com
Subject: Re: [PATCH v4 4/4] gdb: Skip trampoline frames in the stack for printing or finish command.
Date: Wed, 02 Aug 2023 14:52:59 +0300 [thread overview]
Message-ID: <83sf91zmn8.fsf@gnu.org> (raw)
In-Reply-To: <20230801224744.24433-5-abdul.b.ijaz@intel.com> (message from Abdul Basit Ijaz on Wed, 2 Aug 2023 00:47:44 +0200)
> From: Abdul Basit Ijaz <abdul.b.ijaz@intel.com>
> Cc: abdul.b.ijaz@intel.com,
> JiniSusan.George@amd.com,
> tom@tromey.com,
> eliz@gnu.org,
> blarsen@redhat.com
> Date: Wed, 2 Aug 2023 00:47:44 +0200
>
> Before the change, GDB prints the frames indicated by the compiler with DIE
> "DW_AT_trampoline" in the backtrace and finish command, but for better user
> experience, all such frames can be hidden from the user. So, after this
> change, now such frames are not printed any more in the backtrace command
> and also the 'finish' command skips the trampoline calls.
Thanks, I believe I already approved the documentation parts of this,
right?
next prev parent reply other threads:[~2023-08-02 11:52 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-08-01 22:47 [PATCH v4 0/4] GDB support for DW_AT_trampoline Abdul Basit Ijaz
2023-08-01 22:47 ` [PATCH v4 1/4] gdb, dwarf: add support for DW_AT_trampoline in DWARF reader Abdul Basit Ijaz
2023-08-02 20:07 ` Tom Tromey
2023-08-07 14:43 ` Ijaz, Abdul B
2023-08-10 16:20 ` Tom Tromey
2023-08-02 20:13 ` Tom Tromey
2023-08-07 13:36 ` Ijaz, Abdul B
2023-08-10 16:18 ` Tom Tromey
2023-08-14 21:53 ` Ijaz, Abdul B
2023-08-01 22:47 ` [PATCH v4 2/4] gdb/symtab: add lookup for trampoline functions Abdul Basit Ijaz
2023-08-02 20:18 ` Tom Tromey
2023-08-07 7:40 ` Ijaz, Abdul B
2023-08-01 22:47 ` [PATCH v4 3/4] gdb/infrun: handle stepping through functions with DW_AT_trampoline Abdul Basit Ijaz
2023-08-02 11:52 ` Eli Zaretskii
2023-08-02 11:54 ` Ijaz, Abdul B
2023-08-02 20:33 ` Tom Tromey
2023-08-07 8:08 ` Ijaz, Abdul B
2023-08-10 16:56 ` Tom Tromey
2023-08-16 14:18 ` Ijaz, Abdul B
2023-08-01 22:47 ` [PATCH v4 4/4] gdb: Skip trampoline frames in the stack for printing or finish command Abdul Basit Ijaz
2023-08-02 11:52 ` Eli Zaretskii [this message]
2023-08-02 11:54 ` Ijaz, Abdul B
2023-08-02 20:41 ` Tom Tromey
2023-08-07 13:28 ` Ijaz, Abdul B
2023-08-10 17:45 ` Tom Tromey
2023-08-02 20:42 ` Tom Tromey
2023-08-07 7:19 ` Ijaz, Abdul B
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=83sf91zmn8.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=JiniSusan.George@amd.com \
--cc=abdul.b.ijaz@intel.com \
--cc=blarsen@redhat.com \
--cc=gdb-patches@sourceware.org \
--cc=tom@tromey.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).