From: Thiago Jung Bauermann <thiago.bauermann@linaro.org>
To: gdb-patches@sourceware.org
Cc: "Aktemur, Tankut Baris" <tankut.baris.aktemur@intel.com>,
Simon Marchi <simark@simark.ca>,
"Maciej W. Rozycki" <macro@orcam.me.uk>
Subject: [PATCH 0/2] Improvements to a few GDB frame unwind functions
Date: Fri, 10 Jan 2025 13:43:58 -0300 [thread overview]
Message-ID: <20250110164430.3376697-1-thiago.bauermann@linaro.org> (raw)
Hello,
These patches grew out of patch 2 of my series¹:
[RFC PATCH v4 00/15] gdbserver improvements for AArch64 SVE support
Simon suggested me to split it into two patches and post them separately,
so here goes.
The second patch incorporates review comments from Baris and Simon.
It has a changelog describing them.
Thiago Jung Bauermann (2):
GDB: frame: Make VALUEP argument optional in frame_register_unwind
GDB: Use gdb::array_view for buffers used in register reading and
unwinding
gdb/amd64-windows-tdep.c | 4 ++--
gdb/frame.c | 26 +++++++++++++---------
gdb/frame.h | 10 ++++-----
gdb/mips-tdep.c | 48 ++++++++++++++++++++++------------------
gdb/stack.c | 2 +-
5 files changed, 50 insertions(+), 40 deletions(-)
¹ https://inbox.sourceware.org/gdb-patches/20241102025635.586759-1-thiago.bauermann@linaro.org/
base-commit: 07492186894c3eda4242e9994fc5e973b8f3fb0b
next reply other threads:[~2025-01-10 16:45 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-01-10 16:43 Thiago Jung Bauermann [this message]
2025-01-10 16:43 ` [PATCH 1/2] GDB: frame: Make VALUEP argument optional in frame_register_unwind Thiago Jung Bauermann
2025-01-10 17:02 ` Simon Marchi
2025-01-10 22:23 ` Thiago Jung Bauermann
2025-01-10 16:44 ` [PATCH 2/2] GDB: Use gdb::array_view for buffers used in register reading and unwinding Thiago Jung Bauermann
2025-01-10 17:45 ` Simon Marchi
2025-01-10 22:28 ` Thiago Jung Bauermann
2025-01-11 13:54 ` Tom de Vries
2025-01-11 15:46 ` Thiago Jung Bauermann
2025-01-11 16:01 ` Tom de Vries
2025-01-12 0:32 ` Thiago Jung Bauermann
2025-01-13 16:40 ` Tom de Vries
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=20250110164430.3376697-1-thiago.bauermann@linaro.org \
--to=thiago.bauermann@linaro.org \
--cc=gdb-patches@sourceware.org \
--cc=macro@orcam.me.uk \
--cc=simark@simark.ca \
--cc=tankut.baris.aktemur@intel.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