[all-commits] [llvm/llvm-project] c5f47c: [lldb-dap] Prevent using an implicit `step-in`. (#...

[Ebuka Ezike via All-commits]

  Branch: refs/heads/main
  Home:   https://github.com/llvm/llvm-project
  Commit: c5f47c6fd2cd9a5d13d20bee2ac7211b28d233e7
      https://github.com/llvm/llvm-project/commit/c5f47c6fd2cd9a5d13d20bee2ac7211b28d233e7
  Author: Ebuka Ezike <yerimyah1 at gmail.com>
  Date:   2025-07-03 (Thu, 03 Jul 2025)

  Changed paths:
    M lldb/packages/Python/lldbsuite/test/tools/lldb-dap/lldbdap_testcase.py
    M lldb/test/API/tools/lldb-dap/step/TestDAP_step.py
    M lldb/test/API/tools/lldb-dap/step/main.cpp
    A lldb/test/API/tools/lldb-dap/step/other.h
    M lldb/tools/lldb-dap/DAP.cpp
    M lldb/tools/lldb-dap/DAP.h
    M lldb/tools/lldb-dap/JSONUtils.cpp

  Log Message:
  -----------
  [lldb-dap] Prevent using an implicit `step-in`. (#143644)

When there is a function that is inlined at the current program counter.
If you get the current `line_entry` using the program counter's address
it will point to the location of the inline function that may be in
another file. (this is in implicit step-in and should not happen what
step over is called).

Use the current frame to get the `line_entry`



To unsubscribe from these emails, change your notification settings at https://github.com/llvm/llvm-project/settings/notifications