Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Pawel Kupczak <pawel.kupczak@intel.com>
To: gdb-patches@sourceware.org
Subject: [PATCH 0/3] extending the amd64 prologue analyzer
Date: Tue,  1 Jul 2025 10:47:56 +0000	[thread overview]
Message-ID: <20250701104759.52595-1-pawel.kupczak@intel.com> (raw)

Hi all,

These 3 patches aim to extend the amd64 prologue analyzer, somewhat in
parallel to how i386 has been doing it already.  This should improve
debugging experience without debug information present.

Looking forward to your feedback!

With regards,
Paweł

Pawel Kupczak (3):
  gdb, amd64: extend the amd64 prologue analyzer to skip register pushes
  gdb, amd64: return after amd64_analyze_frame_setup if current_pc
    reached
  gdb, amd64: extend the amd64 prologue analyzer to skip stack alloc

 gdb/amd64-tdep.c                              | 124 +++++++++++++++++-
 .../amd64-extended-prologue-analysis.c        |  56 ++++++++
 .../amd64-extended-prologue-analysis.exp      |  86 ++++++++++++
 3 files changed, 265 insertions(+), 1 deletion(-)
 mode change 100644 => 100755 gdb/amd64-tdep.c
 create mode 100644 gdb/testsuite/gdb.arch/amd64-extended-prologue-analysis.c
 create mode 100644 gdb/testsuite/gdb.arch/amd64-extended-prologue-analysis.exp

-- 
2.34.1

---------------------------------------------------------------------
Intel Technology Poland sp. z o.o.
ul. Slowackiego 173 | 80-298 Gdansk | Sad Rejonowy Gdansk Polnoc | VII Wydzial Gospodarczy Krajowego Rejestru Sadowego - KRS 101882 | NIP 957-07-52-316 | Kapital zakladowy 200.000 PLN.
Spolka oswiadcza, ze posiada status duzego przedsiebiorcy w rozumieniu ustawy z dnia 8 marca 2013 r. o przeciwdzialaniu nadmiernym opoznieniom w transakcjach handlowych.

Ta wiadomosc wraz z zalacznikami jest przeznaczona dla okreslonego adresata i moze zawierac informacje poufne. W razie przypadkowego otrzymania tej wiadomosci, prosimy o powiadomienie nadawcy oraz trwale jej usuniecie; jakiekolwiek przegladanie lub rozpowszechnianie jest zabronione.
This e-mail and any attachments may contain confidential material for the sole use of the intended recipient(s). If you are not the intended recipient, please contact the sender and delete all copies; any review or distribution by others is strictly prohibited.

             reply	other threads:[~2025-07-01 10:50 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-07-01 10:47 Pawel Kupczak [this message]
2025-07-01 10:47 ` [PATCH 1/3] gdb, amd64: extend the amd64 prologue analyzer to skip register pushes Pawel Kupczak
2025-07-18 13:43   ` Guinevere Larsen
2025-07-18 15:15     ` Kupczak, Pawel
2025-07-23 10:34       ` Kupczak, Pawel
2025-07-23 16:07         ` Guinevere Larsen
2025-07-18 15:23     ` Andrew Burgess
2025-07-18 16:04       ` Schimpe, Christina
2025-07-01 10:47 ` [PATCH 2/3] gdb, amd64: return after amd64_analyze_frame_setup if current_pc reached Pawel Kupczak
2025-07-18 13:46   ` Guinevere Larsen
2025-07-18 15:19     ` Kupczak, Pawel
2025-07-18 14:46   ` Andrew Burgess
2025-07-18 15:21     ` Kupczak, Pawel
2025-07-01 10:47 ` [PATCH 3/3] gdb, amd64: extend the amd64 prologue analyzer to skip stack alloc Pawel Kupczak
2025-07-15  7:37 ` [PING] [PATCH 0/3] extending the amd64 prologue analyzer Kupczak, Pawel

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=20250701104759.52595-1-pawel.kupczak@intel.com \
    --to=pawel.kupczak@intel.com \
    --cc=gdb-patches@sourceware.org \
    /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