You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
andrewcrawley opened this issue
Apr 26, 2016
· 2 comments
Assignees
Labels
bugIssue identified by VS Code Team member as probable bugdebugDebug viewlet, configurations, breakpoints, adapter issuesverifiedVerification succeeded
Set a breakpoint on line 7 (the body of the test function)
When the breakpoint is hit, expand all the threads so you can see their stack frames
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.
bpasero
added
bug
Issue identified by VS Code Team member as probable bug
debug
Debug viewlet, configurations, breakpoints, adapter issues
labels
Apr 26, 2016
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Labels
bugIssue identified by VS Code Team member as probable bugdebugDebug viewlet, configurations, breakpoints, adapter issuesverifiedVerification succeeded
Steps to Reproduce:
g++ -g -std=c++11 -pthread hello.cpp -o hello
test
function)clone
orcreate_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()
ortest()
) 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
The text was updated successfully, but these errors were encountered: