Hello,
    We have been using VM for about 2 years now and were only able to use the GDB debugger on VS 2015. However, due to the support being dropped from 2015, we feel pressured to get the VS 2017 debugger working for an Arduino Zero. The problem is that the debugger initialization sequence always hangs. The most common point of hang seems to be when the debugger is attempting to load symbols from one of the *.elf files. Build succeeds, everything is up to date, and we are able to upload/run the project without debugging. So I am curious as to how we can fix this issue with the debugger or symbols loading. Thank you

Hi,

Which version of visual micro do you have installed in vs2015?
Which version of Arduino ide?
You can find a gdb logs folder below the project\debug or project\release folder.

Please zip and email both logs folders from vs2017 and vs2015 to info[at]visualmicro.com

Thanks

Just uploaded log files to info[at]visualmicro.com.
In VS 2017:
    - VM Arduino IDE version: 1805.25.0
    - VM GDB 2017: 15.170821.1

I do have the Android C++ tools.
In VS 2015:
    - VM Arduino IDE version: 1805.25.0
    - VM GDB 2015: 14.170501.1

The problem in VS2015: Debugger starts, however we cannot insert break points before or during debugging, no matter how many times we build.

1)
Do the logs you sent include the working logs for vs2015?

2)

The gdb debugger certainly needs the android tools

The gdb is outside of visual micro and beta because it relies on tools such as android which are difficult to support.

Over the coming months visual micro will discontinue support for vs2012 and 2013. This will then allow is to include gdb directly in visual micro. Unfortunately Microsoft have changed their api format so we can't combine into one as things stand.

Let's see what happens if you install android for vs2017

That makes sense, and we would prefer to use VS 2017 since the only reason we keep VS2015 around is for arduino zero debugging. As for the Android C++ tools I will reiterate myself above in that we do have them installed. We uninstalled and reinstalled VM and the tools in all possible orders.

As for the logs, if 2017 and 2015 use the same folder, then yes it probably includes both. I can delete the log directory and just debug in 2017 for more specific logs if needed.

So the logs were all created by VS 2015. I deleted the Debug/ directory and started a debug session by VS 2017 only. It recreated the Debug/ directory, however there wasn't a lower logs/ directory or VM_DBG/ directory. The debugger hung, then timed out. The task manager shows MicroDebug.exe running. Not sure what is causing it to hang.

We will do some tests over the next 10-14 days. Thanks for the info.

I was able to create a new blink project in a fresh install of visual studio 2017 with all required tools. I'll send info[at]visualmicro.com the logs from this project which were only created by VS2017. Hopefully that will be of more help. Thanks

vMicro now supports a range of additional hardware debuggers out of the box:

Debugger List: https://www.visualmicro.com/page/DebuggerSupportList.aspx