CLion 2019.3.5 bug-fix update

A new bug-fix update, CLion 2019.3.5, is now available for download! You can get build 193.6911.21 from our website, via the Toolbox App, or as a snap package (for Ubuntu). A patch update will be available shortly.


Here are the main highlights of the update:

  • The IDE UI freeze while debugging has been fixed (CPP-18278).
  • Formatter improvements:
    • Fixed the incorrect formatting of the macros used inside the macro argument (CPP-18644).
    • Fixed the incorrect formatting of the strings concatenation used inside macro calls (CPP-18628).
  • VCS: commit actions are no longer disabled on a commit of a deleted file (IDEA-225882).
  • More fixes from the IntelliJ Platform.

Full release notes are available here.

Additionally, the CLion 2020.1 EAP is now up and running. It brings CUDA enhancements, support for Clang-cl and IAR compilers, the ability to debug customer targets, Data Flow Analysis rewritten on Clang, a PlatformIO plugin, and more. For more details please see this page.

Your CLion team
The Drive to Develop

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

7 Responses to CLion 2019.3.5 bug-fix update

  1. Taw says:

    Anastasia, I feel the need to tell you that the 2020.1 EAP is the most buggish EAP ever, I am still relying on 2019.3.3 and I am not sure if to update to 3.5.
    It’s not CLion’s team fault, but the latest IDEA is not polished at all.

    For example look at this silly bug CPP-19527, which worked perfectly till now…and they are many others, I think that I opened at least 15 bugs on the latest EAP.

    • Anastasia Kazakova says:

      Thank you, the overall impression is definitely important. We are on the issues you’ve logged. Stay tuned.

  2. Taw says:

    Thank you.
    A short question: is it a simple way to switch the toolchain for each project?
    I have a project which I need to compile with gcc-8 and another one with 4.9.


    • Anastasia Kazakova says:

      I guess the easiest way is to keep 2 toolchains configured. And one CMake profile. And switch toolchains used in the CMake profile.
      But if that’s two separate projects, then simply configure both toolchains and created different CMake profiles (one with gcc-8 and one with 4.9 toolchain used). Toolchains are per IDE. CMake profiles are per project.

Leave a Reply

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