Open AlanRosenthal opened 7 years ago
@AlanRosenthal if this is the entire engine log, I see we're expecting to find Thread but gdb doesn't look like it ever sent us the thread created event for id
2` (named Thread 1) which is why we are not able to debug. This doesn't look like a VSCode issue, more like a gdb issue.
I'm able to successfully use gdb without vscode.
Vscode used to successfully debug with my current settings.
On Fri, Jun 16, 2017, 3:23 PM Pierson Lee notifications@github.com wrote:
@AlanRosenthal https://github.com/alanrosenthal if this is the entire engine log, I see we're expecting to find Thread but gdb doesn't look like it ever sent us the thread created event for id2` (named Thread 1) which is why we are not able to debug. This doesn't look like a VSCode issue, more like a gdb issue.
— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub https://github.com/Microsoft/vscode-cpptools/issues/831#issuecomment-309113351, or mute the thread https://github.com/notifications/unsubscribe-auth/ABOqwVPp4oKj7NaXvgxnqT3JwaSxxLTYks5sEtZBgaJpZM4N8l7q .
Does your scenario work with Stable VS Code?
Both no longer work
On Fri, Jun 16, 2017, 5:00 PM Pierson Lee notifications@github.com wrote:
Does your scenario work with Stable VS Code?
— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub https://github.com/Microsoft/vscode-cpptools/issues/831#issuecomment-309132972, or mute the thread https://github.com/notifications/unsubscribe-auth/ABOqwSd7XhiwPbJwBS5xvUjlFz0iilXXks5sEuzdgaJpZM4N8l7q .
Latest Insiders
Version 1.14.0-insider Commit 73015a5e052e6de8ecd60eed2670bea81fad8cac Date 2017-06-16T05:10:46.035Z Shell 1.6.6 Renderer 56.0.2924.87 Node 7.4.0
Ubuntu 16.04 x64Here's the Debug Console Log: