[macOS Catalina] Unable to debug with 'externalConsole': true #5079
Comments
|
Can you run |
|
|
Thank you! Can you enable DevToolsSecurity? You can do that by running Do you still encounter the issue when you start debugging after that? |
Yes, I am still having the same issue. |
|
@sourav-dey Thanks for all the info. I will need to grab a new machine and see if I can reproduce this issue. What version of XCode are you using? |
|
Cool, sure. |
|
From @lmapii
|
|
From @peza8
|
|
@peza8 Could you provide some additional info for me? What version of VS Code are you using?
|
|
Hey @WardenGnaw , here's the info: 1. VSCode version: 2. Version of the C/C++ extension: 0.27.1 3. Xcode version: 11.3.1 4. Logs are attached: Other [potentially] useful info:
|
|
@peza8 Your issue is that you are using
You will want to use |
|
@WardenGnaw - This does cause an external terminal window to open, but the application still doesn't run. Updated logs attached. |
|
@peza8 I think can repro this. The issue seems to be when we have Can you hit a breakpoint in your main function if you set |
|
Yes, that what I tried to indicate in my second bullet of the section Other [potentially] useful info: in this message above. With |
This comment was marked as off-topic.
This comment was marked as off-topic.
This comment was marked as off-topic.
This comment was marked as off-topic.
This comment was marked as off-topic.
This comment was marked as off-topic.
|
The issue is when VSCode launches the debug adapter, then the debug adapter launches
You can run this specific task using Once you allow this permission, then the external console should appear when you debug. |
|
@WardenGnaw There is a typo in your task, there is an extra |
|
Workaround works! Well done and thank you @WardenGnaw ! |
|
so useful, thanks |
|
I'm running into what appears to be the same issue, but the workaround suggested by @WardenGnaw doesn't work for me. I ran the "Open Terminal" task as suggested, and I got the prompt as expected: However, when I start the debugging session, I just get two empty terminal windows and the debugger doesn't stop at the breakpoint:
Here's the output from the debug console:
|
|
Tried the proposed solution. I am not being prompted to allow terminal, instead the terminal opens up with just hello. No luck on my end. Any ideas? |
change this works for me with @KingOfDuck solution |
|
For anyone still having this issue. After you follow the steps to make the terminal pop up. Make sure you have the configuration |
|
same issue with MacBook m1, console opens but nothing appears, only that: |
|
The same issue on m1. |
|
Same issue here: it works on Intel Mac, it doesn't on M1. |
|
@ahmadrazakhawaja: that's a problem of white spaces - not of the M1 chip. Your working directory seems to contain many spaces ("1.3 Linux Socket in C"), and it's always a very bad idea to have spaces in your path. If not escaped properly they'll cause troubles when used as arguments in a command... and guess what happened ? |
|
@TommyPec: Thanks, Sorry for disturbing for such a trivial issue. Yup you were right fixing the spaces solved the problem. Just to be clear I have the intel Mac. |

Formed in 2009, the Archive Team (not to be confused with the archive.org Archive-It Team) is a rogue archivist collective dedicated to saving copies of rapidly dying or deleted websites for the sake of history and digital heritage. The group is 100% composed of volunteers and interested parties, and has expanded into a large amount of related projects for saving online and digital history.






Type: Debugger
OS: MacOS
Version: 10.15.3
Debugger: LLDB
cpptools version: Version 0.27.0-insiders2
launch.json:
tasks.json:
Logs:
Opens up a external terminal window with log:
Followed: https://code.visualstudio.com/docs/cpp/config-clang-mac
Now I need to run twice or thrice sometimes for the debugger to work properly with the same code.
The text was updated successfully, but these errors were encountered: