[binutils-gdb] Rename one DAP function
Tom Tromey
tromey@sourceware.org
Mon Jun 12 18:13:39 GMT 2023
https://sourceware.org/git/gitweb.cgi?p=binutils-gdb.git;h=8c8701f9cf5bcdb07fa318fd93c2c61fea81cba4
commit 8c8701f9cf5bcdb07fa318fd93c2c61fea81cba4
Author: Tom Tromey <tromey@adacore.com>
Date: Tue May 9 14:38:45 2023 -0600
Rename one DAP function
When I first started implementing DAP, I had some vague plan of having
the implementation functions use the same name as the request. I
abandoned this idea, but one vestige remained. This patch renames the
one remaining function to be gdb-ish.
Diff:
---
gdb/python/lib/gdb/dap/next.py | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/gdb/python/lib/gdb/dap/next.py b/gdb/python/lib/gdb/dap/next.py
index 290b9b855ba..75f2fa6f31a 100644
--- a/gdb/python/lib/gdb/dap/next.py
+++ b/gdb/python/lib/gdb/dap/next.py
@@ -56,7 +56,7 @@ def next(*, threadId, singleThread=False, granularity="statement", **args):
@capability("supportsSteppingGranularity")
@capability("supportsSingleThreadExecutionRequests")
@request("stepIn")
-def stepIn(*, threadId, singleThread=False, granularity="statement", **args):
+def step_in(*, threadId, singleThread=False, granularity="statement", **args):
send_gdb(lambda: _handle_thread_step(threadId, singleThread))
cmd = "step"
if granularity == "instruction":
More information about the Gdb-cvs
mailing list