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

Clicking a stack frame with no source causes all other thread stacks to collapse #5784

Closed
andrewcrawley opened this issue Apr 26, 2016 · 2 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

@andrewcrawley
Copy link

  • VSCode Version: master (b2f6194)
  • OS Version: Ubuntu 14.04

Steps to Reproduce:

  1. Compile https://gist.github.com/edumunoz/6e2ca90d4b5d3dbfa5340576e79ac113 with g++ -g -std=c++11 -pthread hello.cpp -o hello
  2. Install the C++ debug adapter
  3. Set a breakpoint on line 7 (the body of the test function)
  4. When the breakpoint is hit, expand all the threads so you can see their stack frames
  5. Click a stack frame that doesn't have source (e.g. clone or create_thread)

At this point, all threads except the one with the frame that was clicked collapse. Clicking a stack frame that has symbols (e.g. main() or test()) doesn't cause any any other threads to collapse.

I would expect that the code view would change to the "Source ... is not available" view without collapsing any of my expanded threads.

@isidorn @weinand

@andrewcrawley
Copy link
Author

Verified that this worked as I'd expect in build 0.10.13-insider.

@bpasero bpasero added bug Issue identified by VS Code Team member as probable bug debug Debug viewlet, configurations, breakpoints, adapter issues labels Apr 26, 2016
@isidorn isidorn added this to the April 2016 milestone Apr 26, 2016
@isidorn
Copy link
Contributor

isidorn commented Apr 29, 2016

@aeschli you are on a linux machine, and all this should work out of the box so giving to you to verify.

@isidorn isidorn assigned aeschli and unassigned isidorn Apr 29, 2016
@aeschli aeschli added the verified Verification succeeded label May 2, 2016
@vscodebot vscodebot bot locked and limited conversation to collaborators Nov 18, 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

4 participants