From: Eli Zaretskii <eliz@gnu.org>
To: Abdul Basit Ijaz <abdul.b.ijaz@intel.com>
Cc: gdb-patches@sourceware.org, JiniSusan.George@amd.com,
tom@tromey.com, blarsen@redhat.com
Subject: Re: [PATCH v5 0/4] GDB support for DW_AT_trampoline
Date: Thu, 17 Aug 2023 08:26:46 +0300 [thread overview]
Message-ID: <83il9e6xyh.fsf@gnu.org> (raw)
In-Reply-To: <20230816215349.6198-1-abdul.b.ijaz@intel.com> (message from Abdul Basit Ijaz on Wed, 16 Aug 2023 23:53:45 +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, 16 Aug 2023 23:53:45 +0200
>
> Changes since V4:
> * Fixed reverse finish for trampolines.
> * Elide trampoline frames in backtrace for frame-filters case.
> * Use target subroutine address instead of name in case of ref type
> trampoline target.
> * Fixed loops formatting and now split line where possible at ";".
>
> V4 series of patches can be found here:
> https://sourceware.org/pipermail/gdb-patches/2023-August/201263.html
No changes in documentation since v4, right?
next prev parent reply other threads:[~2023-08-17 5:26 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-08-16 21:53 Abdul Basit Ijaz
2023-08-16 21:53 ` [PATCH v5 1/4] gdb, dwarf: add support for DW_AT_trampoline in DWARF reader Abdul Basit Ijaz
2023-08-16 21:53 ` [PATCH v5 2/4] gdb/symtab: add lookup for trampoline functions Abdul Basit Ijaz
2023-08-16 21:53 ` [PATCH v5 3/4] gdb/infrun: handle stepping through functions with DW_AT_trampoline Abdul Basit Ijaz
2023-08-16 21:53 ` [PATCH v5 4/4] gdb: Skip trampoline frames in the stack for printing or finish command Abdul Basit Ijaz
2023-08-17 5:26 ` Eli Zaretskii [this message]
2023-08-17 7:37 ` [PATCH v5 0/4] GDB support for DW_AT_trampoline Ijaz, Abdul B
2023-09-03 19:14 ` [PING][PATCH " Ijaz, Abdul B
2023-09-27 21:05 ` [PING 2][PATCH " Ijaz, Abdul B
2023-12-28 11:30 ` [PING 3][PATCH " Ijaz, Abdul B
2024-01-10 7:40 ` George, Jini Susan
2024-01-10 9:22 ` Ijaz, Abdul B
2024-01-10 16:59 ` George, Jini Susan
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=83il9e6xyh.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).