From: Tom Tromey <tom@tromey.com>
To: gdb-patches@sourceware.org
Cc: Tom Tromey <tom@tromey.com>
Subject: [PATCH 1/2] Remove vestiges of MI version 0
Date: Wed, 10 Aug 2022 15:43:15 -0600 [thread overview]
Message-ID: <20220810214316.2591985-2-tom@tromey.com> (raw)
In-Reply-To: <20220810214316.2591985-1-tom@tromey.com>
I found a few vestiges of MI version 0 in the test suite. This patch
removes them.
---
gdb/testsuite/lib/mi-support.exp | 27 ---------------------------
1 file changed, 27 deletions(-)
diff --git a/gdb/testsuite/lib/mi-support.exp b/gdb/testsuite/lib/mi-support.exp
index ca56e12b06b..346140745aa 100644
--- a/gdb/testsuite/lib/mi-support.exp
+++ b/gdb/testsuite/lib/mi-support.exp
@@ -1424,33 +1424,6 @@ proc mi_continue_to {func} {
mi_runto_helper $func "continue"
}
-proc mi0_execute_to { cmd reason func args file line extra test } {
- mi_execute_to_helper "$cmd" "$reason" "$func" "\{$args\}" \
- "$file" "$line" "$extra" "$test"
-}
-
-proc mi0_next_to { func args file line test } {
- mi0_execute_to "exec-next" "end-stepping-range" "$func" "$args" \
- "$file" "$line" "" "$test"
-}
-
-proc mi0_step_to { func args file line test } {
- mi0_execute_to "exec-step" "end-stepping-range" "$func" "$args" \
- "$file" "$line" "" "$test"
-}
-
-proc mi0_finish_to { func args file line result ret test } {
- mi0_execute_to "exec-finish" "function-finished" "$func" "$args" \
- "$file" "$line" \
- ",gdb-result-var=\"$result\",return-value=\"$ret\"" \
- "$test"
-}
-
-proc mi0_continue_to { bkptno func args file line test } {
- mi0_execute_to "exec-continue" "breakpoint-hit\",bkptno=\"$bkptno" \
- "$func" "$args" "$file" "$line" "" "$test"
-}
-
# Creates a breakpoint and checks the reported fields are as expected.
# This procedure takes the same options as mi_make_breakpoint and
# returns the breakpoint regexp from that procedure.
--
2.34.1
next prev parent reply other threads:[~2022-08-10 21:43 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-08-10 21:43 [PATCH 0/2] Remove MI version 1 Tom Tromey
2022-08-10 21:43 ` Tom Tromey [this message]
2022-08-10 21:43 ` [PATCH 2/2] " Tom Tromey
2022-08-23 19:40 ` [PATCH 0/2] " Tom Tromey
2022-08-23 19:42 ` Simon Marchi via Gdb-patches
2022-12-19 14:49 ` 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=20220810214316.2591985-2-tom@tromey.com \
--to=tom@tromey.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