jmdavis_squid

Thanks to both of you for the feedback on the debugging options for the C++ extension. I'll pass this on to to the documentation folks to get better launch.json documentation released.

I know it isn't ideal, but in the meantime, the best way to get more info is probably the comments that appear when hovering over the fields in the launch.json file or to open up the package.json file to read the comments about each available field in the schema for the extension. The package.json can be found in the .vscode sub-folder of your user account. On my machine, this would be ~/.vscode/extensions/ms-vscode.cpptools-0.8.1\package.json.

gdb is available on mac without compiling using macports or downloading using brew. You do have to sign it yourself though as osx blocks debuggers from debugging without a signature. For windows debugging, we suggest using the community edition of Visual Studio (https://www.visualstudio.com/en-us/products/visual-studio-co...)

RHEL 7.2 x64 should work today but requires manual installation steps as described in the extension. We'd love hear feedback on the direction this work should go. There is an insiders group for that purpose available here http://landinghub.visualstudio.com/c-nonwin