You signed in with another tab or window.Reload to refresh your session.You signed out in another tab or window.Reload to refresh your session.You switched accounts on another tab or window.Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: launch.md
+3-1Lines changed: 3 additions & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -22,7 +22,9 @@ Set or change the following options to control VS Code's behavior during debuggi
22
22
Tells_GDB or LLDB_ what paths to search for .so files. Separate multiple paths with a semicolon. Example:`"/Users/user/dir1;/Users/user/dir2"`.
23
23
24
24
*####`externalConsole`
25
-
If set to`true`, launches an external console for the application. If`false`, no console is launched and VS Code's debugging console is used. Note this option is ignored in some cases for technical reasons.
25
+
Windows: When set to true, it will spawn an external console. When set to false, it will use VS Code's integratedTerminal.
26
+
Linux: When set to true, it will notify VS Code to spawn an external console. When set to false, it will use VS Code's integratedTerminal
27
+
macOS: When set to true, it will spawn an external console through`lldb-mi`. When set to false, the output can be seen in VS Code's debugConsole. Due to limitations within`lldb-mi`, integratedTerminal support is not available.
26
28
27
29
*####`logging`
28
30
Optional flags to determine what types of messages should be logged to the Debug Console.