Skip to content

duplicated top stackframe with old debug adapters #28808

@weinand

Description

@weinand

VSCode Version: Insider 1.14.0

  • debug simple program with mono-debug

Observe: the stack frame is duplicated:

2017-06-15_13-06-08

First VS Code asks for stackframes with startFrame = 0 and levels = 1.
Then mono-debug returns all frames (which happens to be exactly one).
Then VS Code asks for stackframes with startFrame = 0 and levels = 20 (probably because the first result did not return the "totalFrames" attribute and VS Code falls back to the old behavior).
Then mono-debug returns all frames again and VS Code adds them to the existing one instead of replacing the existing one.

Then I tried a program where the stacktrace has one additional level but this doesn't make a difference:

2017-06-15_13-18-13

Metadata

Metadata

Assignees

Labels

bugIssue identified by VS Code Team member as probable bugdebugDebug viewlet, configurations, breakpoints, adapter issuesverifiedVerification succeeded

Type

No type

Projects

No projects

Milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions