CLion 2019.2.4 Bug-fix Update


If you are using macOS 10.15 Catalina and the recent CLion release 2019.2.3 (or any CLion version earlier than 2019.2.2), please update to get the LLDB working.


macOS Catalina was finally released a few days ago. We started testing and fixing some issues there well in advance, and CLion 2019.2.2 was released a month ago with a fix for LLDB on Catalina.

Unfortunately, in CLion 2019.2.3 the debugger on Catalina was broken. After the official macOS release, our users have faced an issue when launching the debugger (CPP-17613). We are really sorry about this, and we’re now releasing a new bug-fix update 2019.2.4 with the proper fix included.

We’ve also investigated the issue internally to prevent similar problems in the future.

CLion 2019.3 EAP is not affected and has LLDB working on Catalina.

Please note that some possible warnings (CPP-17268) are still present but don’t seem to prevent debugging. Also, another update CLion 2019.2.5 with more fixes from the IntelliJ Platform, which in particular targets macOS 10.15 Catalina users, will be released in a few weeks. Stay tuned!

Your CLion Team
The Drive to Develop

This entry was posted in Announcement and tagged , , . Bookmark the permalink.

11 Responses to CLion 2019.2.4 Bug-fix Update

  1. Fan says:

    i still can’t run debug on the newest Clion.
    the output is “process exited with status -1 (Error )
    please help me.

  2. ufosky says:

    I have the same issue with CLion 2019.3.4 on macOS.
    When debug use lldb, always get output “process exited with status -1 (Error 1)” and the log:

    2020-02-23 22:31:10,816 [ 20348] DEBUG – brains.cidr.execution.debugger – [protobuf client 1] 1833 res:launch {
    common_response {
    is_valid: false
    error_message: “process exited with status -1 (Error 1)”
    2020-02-23 22:31:10,820 [ 20352] DEBUG – brains.cidr.execution.debugger –
    com.jetbrains.cidr.execution.debugger.backend.lldb.LLDBDriverException: process exited with status -1 (Error 1)
    at com.jetbrains.cidr.execution.debugger.backend.lldb.LLDBDriver$ThrowIfNotValid.throwIfNeeded(
    at com.jetbrains.cidr.execution.debugger.backend.lldb.LLDBDriver.a(
    at com.jetbrains.cidr.execution.debugger.backend.lldb.LLDBDriver.access$800(
    at com.jetbrains.cidr.execution.debugger.backend.lldb.LLDBDriver$7.startImpl(
    at com.jetbrains.cidr.execution.debugger.backend.DebuggerDriver$Inferior.start(
    at com.jetbrains.cidr.execution.debugger.CidrDebugProcess.doStartTarget(
    at com.jetbrains.cidr.execution.debugger.CidrDebugProcess.b(
    at com.jetbrains.cidr.execution.debugger.CidrDebugProcess$
    at com.jetbrains.cidr.execution.debugger.CidrDebugProcess$
    at com.jetbrains.cidr.execution.debugger.CidrDebuggerCommandExecutor$doExecuteCommand$2.invokeSuspend(CidrDebuggerCommandExecutor.kt:95)
    at com.jetbrains.cidr.execution.debugger.CidrDebuggerCommandExecutor$doExecuteCommand$2.invoke(CidrDebuggerCommandExecutor.kt)
    at kotlinx.coroutines.intrinsics.UndispatchedKt.startUndispatchedOrReturn(Undispatched.kt:91)
    at kotlinx.coroutines.BuildersKt__Builders_commonKt.withContext(Builders.common.kt:155)
    at kotlinx.coroutines.BuildersKt.withContext(Unknown Source)
    at com.jetbrains.cidr.execution.debugger.CidrDebuggerCommandExecutor.doExecuteCommand(CidrDebuggerCommandExecutor.kt:88)
    at com.jetbrains.cidr.execution.debugger.CidrDebuggerCommandExecutor.executeCommand(CidrDebuggerCommandExecutor.kt:73)
    at com.jetbrains.cidr.execution.debugger.CidrDebuggerCommandExecutor$executeCommandAsync$1.invokeSuspend(CidrDebuggerCommandExecutor.kt:58)
    at kotlin.coroutines.jvm.internal.BaseContinuationImpl.resumeWith(ContinuationImpl.kt:33)
    at com.intellij.util.concurrency.BoundedTaskExecutor.doRun(
    at com.intellij.util.concurrency.BoundedTaskExecutor.access$200(
    at com.intellij.util.concurrency.BoundedTaskExecutor$1.execute(
    at com.intellij.util.ConcurrencyUtil.runUnderThreadName(
    at com.intellij.util.concurrency.BoundedTaskExecutor$
    at java.base/java.util.concurrent.ThreadPoolExecutor.runWorker(
    at java.base/java.util.concurrent.ThreadPoolExecutor$
    at java.base/
    2020-02-23 22:31:10,840 [ 20372] DEBUG – brains.cidr.execution.debugger – [protobuf client 1] 1858 req(7): kill {
    2020-02-23 22:31:10,842 [ 20374] DEBUG – brains.cidr.execution.debugger – [protobuf client 1] 1859 res:kill {
    common_response {
    is_valid: true
    2020-02-23 22:31:10,856 [ 20388] DEBUG – brains.cidr.execution.debugger – [protobuf client 1] 1861 req(6): exit {
    2020-02-23 22:31:12,336 [ 21868] INFO – j.ide.plugins.RepositoryHelper – using cached plugin list (updated at 2020/2/23, 22:03)

    Because it works some days before, so I tried to delete all the files related to clion in ~/Library, but still not work. Also I tried use “sudo /Applications/” launch clion, and this time it works.

    The other way for debugging use gdb is not work too, it produce this error: com.jetbrains.cidr.execution.debugger.backend.gdb.GDBDriver$GDBCommandException: “/Users/***/cmake-build-debug/filewrite”: not in executable format: File format not recognized

    • Anastasia Kazakova says:

      Let’s me check and come back to you soon.

      • ufosky says:

        When debug using lldb, if it prompt a window ask for os user password the first time since os started, then it works fine. But now it just produce an error message and no asking for user password.

        • v says:

          Was this ever resolved?

          • Anastasia Kazakova says:

            Do you still experience this issue? With which CLion version?

          • v says:

            I am experiencing this on 2019.3.5.

          • v says:

            Is there a slack channel to chat about this?

          • Anastasia Kazakova says:

            Could you please run this command in terminal: log stream –predicate ‘process = “taskgated” OR (process = “kernel” AND eventMessage CONTAINS “macOSTaskPolicy”)’ –info
            Then look when happens there when you start debugging.
            Also, check in if you have any crash reports maybe.

            Let’s proceed with this data in support – drop a message to clion-support at with the result and a link to this thread.

          • v says:

            Ok I sent an email out to that address with the results. Thank you for your help.

Leave a Reply to ufosky Cancel reply

Your email address will not be published. Required fields are marked *