Skip to content

Documenting options in launch.json #193

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
AndrewBrianHall merged 2 commits into from
Sep 2, 2016
Merged

Documenting options in launch.json #193

Changes from 1 commit
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
d4e89bd
Documenting options in launch.json
Sep 1, 2016
3438563
updates to launch.json doc based on PR feedback
Sep 2, 2016
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
Prev Previous commit
updates to launch.json doc based on PR feedback
  • Loading branch information
Andrew Hall (DEVDIV) committed Sep 2, 2016
commit 343856354e91a6247149729ca96054e533bb3aee
5 changes: 3 additions & 2 deletions launch.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -79,7 +79,7 @@ You can change the behavior of GDB or LLDB by setting the following options.

**MIMode**: Indicates the debugger that VS Code will connect to. Must be set to `gdb` or `lldb`. This is pre-configured on a per-operating system basis and can be changed as needed.

**miDebuggerPath**: The path to the debugger (such as gdb). When unspecified, it will search the operating system's PATH variable first for the debugger. default": "/usr/bin/gdb".
**miDebuggerPath**: The path to the debugger (such as gdb). When unspecified, it will search the operating system's PATH variable for a debugger (GDB on Linux and Windows, LLDB on OS X).

**stopAtEntry**: If set to true, the debugger should stop at the entrypoint of the target (ignored on attach). Default value is `false`.

Expand Down Expand Up @@ -122,7 +122,8 @@ The C/C++ extension enables debugging dump files on Windows and core dump files

**dumpPath**: If you want to debug a Windows dump file, set this to the path to the dump file to start debugging in the `launch` configuration.

**coreDumpPath**: Full path to a core dump file to debug for the specified program. Set this to the path to the core dump file to start debugging in the `launch` configureation.
**coreDumpPath**: Full path to a core dump file to debug for the specified program. Set this to the path to the core dump file to start debugging in the `launch` configuration.
_Note: core dump debuging is not supported with MinGw._

Copy link

@delmyers delmyers Sep 1, 2016

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Note that you can't debug dump files with mingw?

## Remote debugging or debugging with a local debugger server

Expand Down