Skip to content
This repository has been archived by the owner on Jul 15, 2023. It is now read-only.

Shown call stack always of depth 1 with version 0.8.0 #2196

Closed
christian-fortini-zz opened this issue Dec 19, 2018 · 4 comments · Fixed by #2200
Closed

Shown call stack always of depth 1 with version 0.8.0 #2196

christian-fortini-zz opened this issue Dec 19, 2018 · 4 comments · Fixed by #2200
Labels

Comments

@christian-fortini-zz
Copy link

The call stack only shows the current frame when code is stopped at breakpoint. With version 0.7.0, you can see the whole stack (up to 20 I believe). With version 0.8.0, only one frame is shown. This is 100% repro as far as I can tell.

@christian-fortini-zz christian-fortini-zz changed the title Call stack always of depth 1 with version 0.8.0 Shown call stack always of depth 1 with version 0.8.0 Dec 19, 2018
@ToothlessGear
Copy link
Contributor

This issue is a duplicate of #2187.
Adding "stackTraceDepth": 50 to launch.json should resolve this.

@ramya-rao-a: Shouldn't there be a default value, if this is not set?
Otherwise https://github.com/Microsoft/vscode-go/blob/0ee759fd87cd0a44287e7a3a4dd081dde111cfb3/src/debugAdapter/goDebug.ts#L274 is undefined and only returns the top frame.

@hatricker
Copy link

I am seeing the same issue.

@ramya-rao-a
Copy link
Contributor

Thanks for reporting @christian-fortini and @hatricker

@ToothlessGear Yes, you are right. We should have a default there. @segevfiner has submitted a PR for the same which I just merged.

To get the fix, please use the latest beta version of this extension

@christian-fortini-zz
Copy link
Author

christian-fortini-zz commented Jan 3, 2019 via email

@vscodebot vscodebot bot locked and limited conversation to collaborators Feb 13, 2019
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
Projects
None yet
Development

Successfully merging a pull request may close this issue.

4 participants