Skip to content

Debugger treats local packages as "external packages", and doesn't debug by default #1497

@kinex

Description

@kinex

When code execution stops to a breakpoint (or to an exception), the source file and line where the breakpoint is located is not activated automatically in the editor window. You have to click the topmost line in the "Call stack" window to see the correct source location in the editor window. Execution point in the editor window is lost again every time you continue debugging with commands like Step Over or Step Into. So you have to continuously click the correct line in the "Call stack" window to see the correct line in the editor window.

This issue makes the debugging experience terribly bad. There was not this issue earlier, but unfortunately I cannot remember the exact time when this problem occurred.

Metadata

Metadata

Assignees

No one assigned

    Labels

    in debuggingRelates to the debug adapter or process of running debug sessionsis bug

    Type

    No type

    Projects

    No projects

    Milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions