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 --git a/gdb/python/lib/gdb/dap/next.py b/gdb/python/lib/gdb/dap/next.py
index 290b9b855bad03d715cbc3e7379ac6652d365cd9..75f2fa6f31ac5fad00d97b33d115a8c4735a71f3 100644 (file)
--- 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":