Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Only get 20 stack frames in chrome debugger #25594

Closed
JonathanMEdwards opened this issue Apr 28, 2017 · 5 comments
Closed

Only get 20 stack frames in chrome debugger #25594

JonathanMEdwards opened this issue Apr 28, 2017 · 5 comments
Assignees
Labels
bug Issue identified by VS Code Team member as probable bug debug Debug viewlet, configurations, breakpoints, adapter issues verified Verification succeeded
Milestone

Comments

@JonathanMEdwards
Copy link
Contributor

  • VSCode Version: Code 1.11.2 (6eaebe3, 2017-04-13T07:56:42.517Z)
  • OS Version: Darwin x64 16.5.0
  • Extensions:
Extension Author Version
ExtensionUpdateCheck HookyQR 0.0.2
vscode-npm-script eg2 0.1.9
auto-close-tag formulahendry 0.3.11
backspace-plusplus jrieken 0.0.15
Theme-MaterialKit ms-vscode 0.1.4
debugger-for-chrome msjsdiag 3.0.1
theme-black-plus none 0.0.1
theme-visualstudio black none 0.0.1

Steps to Reproduce:

@isidorn
Copy link
Contributor

isidorn commented Apr 28, 2017

@JonathanMEdwards There is a button load more stack frames - did you try that?
Please provide more details as to what is the actual issue

@isidorn isidorn added debug Debug viewlet, configurations, breakpoints, adapter issues info-needed Issue requires more information from poster labels Apr 28, 2017
@JonathanMEdwards
Copy link
Contributor Author

JonathanMEdwards commented Apr 28, 2017

screen shot 2017-04-28 at 6 58 45 am
There is no such button I can find. Where is it supposed to be?

@isidorn
Copy link
Contributor

isidorn commented Apr 28, 2017

@JonathanMEdwards if there are more stack frames you should see an option to show more on the bottom of the callstack view. If we are not showing this it is because we are not getting more from the chrome debug extension -> assigning to @roblourens

@isidorn isidorn removed their assignment Apr 28, 2017
@JonathanMEdwards
Copy link
Contributor Author

JonathanMEdwards commented Apr 28, 2017 via email

@roblourens roblourens added bug Issue identified by VS Code Team member as probable bug and removed info-needed Issue requires more information from poster labels Apr 28, 2017
@roblourens roblourens added this to the May 2017 milestone Apr 28, 2017
@roblourens
Copy link
Member

roblourens commented Jun 5, 2017

Verifier - verify with either node (inspector) or chrome debugger.

@isidorn isidorn added the verified Verification succeeded label Jun 6, 2017
@vscodebot vscodebot bot locked and limited conversation to collaborators Nov 17, 2017
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
bug Issue identified by VS Code Team member as probable bug debug Debug viewlet, configurations, breakpoints, adapter issues verified Verification succeeded
Projects
None yet
Development

No branches or pull requests

3 participants