No longer able to debug

[AlanRosenthal]

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 x64

Here's the Debug Console Log:

=thread-group-added,id="i1"
GNU gdb (GNU Tools for ARM Embedded Processors) 7.10.1.20151217-cvs
Copyright (C) 2015 Free Software Foundation, Inc.
License GPLv3+: GNU GPL version 3 or later <http://gnu.org/licenses/gpl.html>
This is free software: you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law.  Type "show copying"
and "show warranty" for details.
This GDB was configured as "--host=i686-linux-gnu --target=arm-none-eabi".
Type "show configuration" for configuration details.
For bug reporting instructions, please see:
<http://www.gnu.org/software/gdb/bugs/>.
Find the GDB manual and other documentation resources online at:
<http://www.gnu.org/software/gdb/documentation/>.
For help, type "help".
Type "apropos word" to search for commands related to "word".
=cmd-param-changed,param="pagination",value="off"
[New Thread 1]
1: (11415) <-1011-interpreter-exec console "info sharedlibrary"
1: (11415) ->~"No shared libraries loaded at this time.\n"
1: (11416) ->1011^done
1: (11416) ->(gdb)
1: (11416) 1011: elapsed time 1
E output: {"category":"console","output":"Loaded 'shared libraries loaded at this time.'. Cannot find or open the symbol file.\n","data":null,"type":"output"}
Loaded 'shared libraries loaded at this time.'. Cannot find or open the symbol file.
1: (11427) <-1012-thread-info
1: (11428) ->1012^done,threads=[{id="2",target-id="Thread 1",details="ISR",frame={level="0",addr="0x1000eecc",func="Reset_Handler",args=[],file="build/startup.sx",fullname="/home/arosenthal/Documents/code/fw-bison/products/boson/gcc/build/startup.sx",line="420"},state="stopped"}],current-thread-id="1"
1: (11428) ->(gdb)
1: (11429) 1012: elapsed time 2
E output: {"category":"stderr","output":"ERROR: Unable to start debugging. Failed to find thread 1 for break event\n","data":null,"type":"output"}
ERROR: Unable to start debugging. Failed to find thread 1 for break event
1: (11442) <--gdb-exit
1: (11442) ->^exit
1: (11443) ->=thread-group-exited,id="i1"
E output: {"category":"console","output":"The program '/home/arosenthal/Documents/code/code.elf' has exited with code 42 (0x0000002a).\r\n\n","data":null,"type":"output"}
The program '/home/arosenthal/Documents/code/code.elf' has exited with code 42 (0x0000002a).
E exited: {"exitCode":42,"type":"exited"}
E terminated: {"type":"terminated"}
E output: {"category":"telemetry","output":"VS/Diagnostics/Debugger/DebugCompleted","data":{"VS.Diagnostics.Debugger.ImplementationName":"Microsoft.MIDebugEngine","VS.Diagnostics.Debugger.EngineVersion":"14.0.40526.1","VS.Diagnostics.Debugger.HostVersion":"1.0.30525.1","VS.Diagnostics.Debugger.AdapterId":"cppdbg","VS.Diagnostics.Debugger.DebugCompleted.BreakCounter":0},"type":"output"}
C disconnect: {"restart":false}
 R: {"success":true,"message":null,"request_seq":13,"command":"disconnect","body":null,"running":false,"refs":null,"seq":0,"type":"response"}

[pieandcakes]

@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.

[AlanRosenthal]

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 .

[pieandcakes]

Does your scenario work with Stable VS Code?

[AlanRosenthal]

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 .