Can't debug on macOS Catalina (LLDB) #3829
Assignees
Labels
Milestone
Comments
|
Can you share the output when you enable logging? |
WardenGnaw
added
debugger
more info needed
LLDB Engine Logging |
|
From the logs, it looks like the breakpoint is ready: But your program is recieving a SIGINT and exiting: Do you stop if you enable |
stopAtEntry is already set to true from the json file that I have provided, and no it does not stop sadly |
|
Not sure if the problem is related, but breakpoints stopped working for me when I upgraded to the macOS Catalina and Xcode11 betas (not sure if the bug is triggered by the macOS or Xcode update). Both "Stop At Entry" as well as breakpoints don't work (neither breakpoints set before the debugging session starts, nor breakpoints set during the debugging session). Using the CodeLLDB extension still works fine btw. Debug log from the C/CPP Extension Debugger: |
Hi, sorry I forgot that I had updated to Catalina...I do not however have the Xcode beta. I'm guessing since we are both experiencing the issue, that it is a 10.15 beta issue. codelldb works however, I can confirm! |
|
Ping. Just wanted to mention that the problem persists with the latest Catalina Beta and Xcode11 "Gold Master" version, both pretty late in their release cycle, so I think that's not something that will be fixed on Apple's part. Also the CodeLLDB extension doesn't have the problem. |
|
Same problem. |
|
Just spent the last hour banging my head against the table trying to figure out what I was doing wrong and then I find this issue! So add me to the list of effected users. I'm on Catalina, VSCode 1.38.1, C/C++ extension 0.26.0-insiders2, Xcode 11 so all the default Apple clang, lldb, etc. |
WardenGnaw
added
bug
and removed
more info needed
WardenGnaw
changed the title
|
This is an issue with the lldb-mi that the extension ships with. A temporary work around would to be set your This workaround may have issues with debugging since there is a difference in the version cpptools extension releases and the version in Xcode. |
|
@WardenGnaw |
|
Also seeing this. macOS Catalina and I need to install CodeLLDB extension to get things working. |
|
@WardenGnaw Thx for solution! It's work for me. |
|
@WardenGnaw no luck with work around, error like @hologerry have. But I'v try to find some valid path using paths: |
|
@hologerry @WardenGnaw The workaround does not work for me either, there's no |
|
The CodeLLDB extension will get this working. |
|
I have the CodeLLDB extension installed and do indeed use this as a workaround for debugging, but I don't understand how it makes the proposed workaround for the C/C++ extension work (I can't find a lldb-mi file in the CodeLLDB's extension directory either). |
|
@WardenGnaw My (clean) install of Catalina with Xcode only has lldb not lldb-mi |
|
I found a workaround:
|
|
We are aware of issues on macOS Catalina and the version of lldb/lldb-mi that comes bundled with the extension. The current workaround is to point Another temporary workaround would be to use a different LLDB extension such as CodeLLDB for debugging on macOS Catalina.” |
|
lldb-mi from XCode 10.1 seems to work as well, at least for c code. |
|
you have to set |
Same problem https://github.com/microsoft/vscode/issues/92202 |
Thank you for your reply, but I can not find the |
|
Quoting the maintainers @sean-mcmanus
Quoting me from further up, if you don't/can't use that: https://github.com/puremourning/lldb-mi/releases instructions: Or use the insiders release per the comments from the maintainer. |
|
after following your instructions (#3829 (comment)) I was facing some issues.
System: macOS 10.15.3 |
I've had a similar issue on 10.15.3. Couldn't get CodeLLDB or the |
|
I still have question here with insiders5. My probelm is if set externalConsole false, it will start debugging but no where to get input. (seems not able to input in debug console, but output there is fine)
|
@Garithe this is a limitation of LLDB, not vscode-cpptools (it also applies to
This is likely a different issue, probably reolated to the |
@puremourning Thanks for replying. But that's just a mistake when I copy the content.I did use "${fileDirname}/${fileBasenameNoExtension}". If it's a name thing, debugger shouldn't run when I set "externalConsole" false. By the way when I click run without debugging there is also nothing in the console, maybe this is indeed another problem |
|
Fixed with 0.27.0. |
|
Yeah, the 0.27.0 works well on 10.15.4. Here's my configurations: tasks.json launch.json However, now although I can uninstall the CodeLLDB extension, I can only debug using external console(Terminal.app). It seems there's no option as "IntegratedTerminal" so I can't use the integrated terminal to debug. When using single screen to debug, that would cause inconvenience. Hope you would support "IntegratedTerminal" option. |
|
Thanks @sean-mcmanus! Looks good to me. @Saafo To get the integrated terminal, set |
|
@spinicist I've tried the |
|
I am having the same issue as @Saafo, cant use my debugger |
|
@Saafo That is the expected behaviour. The debugger has its own terminal, that is the "Integrated Terminal". The inability to take input has been a longstanding issue, if you need to provide input to your program then you can use the external console. |
|
@Saafo How do you fix the issue, i have the same issue too. |
|
It's really simple. The integrated terminal is not supported, and never was. |
|
@Kendrick-Song I just can't solve it... I have to use the external terminal now. |
|
I had a very similar problem, but I was able to FINALLY get the debbuger WORKING. So, the one thing I didn't do after setting up my task json file was to press command+shift+B. So to solve the problem I was having, 1)I created a new .c file in a new folder Advice: Especial when you are new to anything(in this case Vscode), when asking a question please mention all the steps you took before you ran into an error/problem. For example: my problem was not pressing cmd+shift+B and had nothing to do with the files themselves. So whoever tries to help on let say github will most likely have no idea that--that's what I'm doing wrong. Also shoutout to @WardenGnaw and all the others that contributed to this. Here is the link to the article that helped with this. The article is for c++ but pretty much the same thing. Now, I did not actual copy and past the code they give because I'm writing in c. The article is on medium so I think the code they provide is save. https://medium.com/gdplabs/build-and-debug-c-on-visual-studio-code-for-mac-77e05537105e |
|
@Kendrick-Song @Saafo read above response might be able to help you guys if you are still interested. |
|
@Chris-Nk maybe you misunderstood what I mean. Press Besides, what we care about is using the I'm not sure whether to open a new issue. |
|
I have installed C/C++ 0.29.0. But I still have the same problem It open a Terminal and do nothing This is my launch.json and this one is task.json macOS 10.15.6 Apple clang version 12.0.0 (clang-1200.0.26.2) lldb-1200.0.26.4 What should I do? |
|
@sean-mcmanus my log: macOS 10.15.6
|
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
and others
Type: Debugger
Input information below
Please review existing issues and our documentation at https://github.com/Microsoft/vscode-cpptools/tree/master/Documentation prior to filing an issue.
Describe the bug
To Reproduce
launch.json
tasks.json
Steps to reproduce the behaviour:
debug using the above tasks and launch files
Additional context
If applicable, please include logging by adding "logging": { "engineLogging": true, "trace": true, "traceResponse": true } in your
launch.jsonAdd any other context about the problem here including log or error messages in your Debug Console or Output windows.
The text was updated successfully, but these errors were encountered: