From: Tom Tromey <tromey@adacore.com>
To: gdb-patches@sourceware.org
Cc: Tom Tromey <tromey@adacore.com>
Subject: [PATCH 0/2] Two small Rust parser changes
Date: Wed, 28 Oct 2026 12:49:32 -0600 [thread overview]
Message-ID: <20261028-rust-no-reset-v1-0-a57eab44c9a5@adacore.com> (raw)
This short series fixes a couple of minor things in the Rust parser.
I think the patches are self-explanatory.
Tested on x86-64 Fedora 43.
Signed-off-by: Tom Tromey <tromey@adacore.com>
---
Tom Tromey (2):
Avoid potential memory leak in Rust parser
Remove rust_parser::reset
gdb/rust-parse.c | 294 +++++++++++++++++++++++++++----------------------------
1 file changed, 142 insertions(+), 152 deletions(-)
---
base-commit: af6a8186d64358c387b6793449be9579f1d40667
change-id: 20261028-rust-no-reset-9edbf14a3dda
Best regards,
--
Tom Tromey <tromey@adacore.com>
next reply other threads:[~2026-10-28 18:50 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-28 18:49 Tom Tromey [this message]
2026-10-28 18:49 ` [PATCH 1/2] Avoid potential memory leak in Rust parser Tom Tromey
2026-10-28 18:49 ` [PATCH 2/2] Remove rust_parser::reset Tom Tromey
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=20261028-rust-no-reset-v1-0-a57eab44c9a5@adacore.com \
--to=tromey@adacore.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