From: Jan Vrany <jan.vrany@labware.com>
To: gdb-patches@sourceware.org
Cc: Jan Vrany <jan.vrany@labware.com>, simark@simark.ca
Subject: Re: [PATCH] gdb: fix possible use-after-free when executing commands
Date: Thu, 15 Dec 2022 14:51:40 +0000 [thread overview]
Message-ID: <20221215145140.39092-1-jan.vrany@labware.com> (raw)
In-Reply-To: <7ced24a4-19d5-293e-b7d6-88d77d3aea7a@simark.ca>
> > + " def invoke (self, arg, from_tty):" "" \
> > + " print (\"redefine_cmd output, msg = %s\" % self._msg)" "" \
> > + " self._msg = arg" "" \
>
> Is it needed to assign arg to self._msg here?
>
It is not, but found it usefull when testing the test.
This way, one may only comment the next line and test would
pass, without need to tweak following `gdb_test` lines.
Removed in new version (below)
> > + " redefine_cmd (arg)" "" \
> > + "redefine_cmd (\"XXX\")" "" \
> > + "end" ""
> > +
> > +gdb_test "redefine_cmd AAA" \
> > + "redefine_cmd output, msg = XXX" \
> > + "call command redefining itself 1"
> > +
> > +gdb_test "redefine_cmd BBB" \
> > + "redefine_cmd output, msg = AAA" \
> > + "call command redefining itself 2"
> > +
>
> Note that in TCL code, we use an indent of 4 columns (and just like with
> C++ code, whole groups of 8 columns become a tab).
>
> In order to isolate the new test from the other tests in the file, can
> you put the new test into its own `proc_with_prefix` function, and start
> with a fresh GDB? That would mean calling clean_restart at the
> beginning of the proc.
Done, hopefully this is what you meant. Also I put the test to the end
of the file, as it is now in its own function.
-- >8 --
Subject: [PATCH v2] gdb/testsuite: add test for Python commands redefining
itself
This commit adds a test that creates a Python command that redefines
itself during its execution. This is to test use-after-free in
execute_command ().
This test needs run with ASan enabled in order to fail when it
should.
---
gdb/testsuite/gdb.python/py-cmd.exp | 30 +++++++++++++++++++++++++++++
1 file changed, 30 insertions(+)
diff --git a/gdb/testsuite/gdb.python/py-cmd.exp b/gdb/testsuite/gdb.python/py-cmd.exp
index aa95a459f46..48c3e18f1cc 100644
--- a/gdb/testsuite/gdb.python/py-cmd.exp
+++ b/gdb/testsuite/gdb.python/py-cmd.exp
@@ -300,3 +300,33 @@ gdb_test_multiple "test_multiline" $test {
pass $test
}
}
+
+# Test command redefining itself
+
+proc_with_prefix test_command_redefining_itself {} {
+ # Start with a fresh gdb
+ clean_restart
+
+
+ gdb_test_multiline "input command redefining itself" \
+ "python" "" \
+ "class redefine_cmd (gdb.Command):" "" \
+ " def __init__ (self, msg):" "" \
+ " super (redefine_cmd, self).__init__ (\"redefine_cmd\", gdb.COMMAND_OBSCURE)" "" \
+ " self._msg = msg" "" \
+ " def invoke (self, arg, from_tty):" "" \
+ " print (\"redefine_cmd output, msg = %s\" % self._msg)" "" \
+ " redefine_cmd (arg)" "" \
+ "redefine_cmd (\"XXX\")" "" \
+ "end" ""
+
+ gdb_test "redefine_cmd AAA" \
+ "redefine_cmd output, msg = XXX" \
+ "call command redefining itself 1"
+
+ gdb_test "redefine_cmd BBB" \
+ "redefine_cmd output, msg = AAA" \
+ "call command redefining itself 2"
+}
+
+test_command_redefining_itself
--
2.35.1
next prev parent reply other threads:[~2022-12-15 14:51 UTC|newest]
Thread overview: 31+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-12-08 14:20 Jan Vrany
2022-12-09 17:55 ` Tom Tromey
2022-12-12 15:05 ` Luis Machado
2022-12-12 15:08 ` Jan Vraný
2022-12-12 15:09 ` Luis Machado
2022-12-13 11:22 ` [PATCH] gdb: fix command lookup in execute_command () Jan Vrany
2022-12-13 15:05 ` Tom Tromey
2022-12-13 16:43 ` Simon Marchi
2022-12-13 18:48 ` Jan Vraný
2022-12-13 19:29 ` Simon Marchi
2022-12-14 11:07 ` [PATCH] gdb: fix command lookup in execute_command () commands" Jan Vrany
2022-12-14 15:35 ` Simon Marchi
2022-12-14 15:41 ` Jan Vraný
2022-12-14 15:59 ` Tom Tromey
2022-12-14 16:01 ` Simon Marchi
2022-12-14 18:05 ` Tom Tromey
2022-12-14 18:30 ` Simon Marchi
2022-12-14 22:01 ` Simon Marchi
2022-12-16 14:07 ` [PATCH] gdb: fix command lookup in execute_command () Jan Vraný
2022-12-16 16:47 ` Simon Marchi
2022-12-19 11:48 ` Jan Vraný
2022-12-19 14:46 ` Tom Tromey
2022-12-19 15:51 ` Jan Vraný
2022-12-20 19:10 ` Tom Tromey
2022-12-14 19:52 ` [PATCH] gdb: fix possible use-after-free when executing commands Simon Marchi
2022-12-14 20:39 ` Jan Vraný
2022-12-14 20:42 ` Simon Marchi
2022-12-15 12:57 ` Jan Vrany
2022-12-15 13:53 ` Simon Marchi
2022-12-15 14:51 ` Jan Vrany [this message]
2022-12-15 16:00 ` Simon Marchi
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=20221215145140.39092-1-jan.vrany@labware.com \
--to=jan.vrany@labware.com \
--cc=gdb-patches@sourceware.org \
--cc=simark@simark.ca \
/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).