CLion 2019.3.4 Bug-fix Update

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

DOWNLOAD CLION

Here are the main highlights of the update:

  • CMake CUDA targets are now launched from CLion using the correct binary (CPP-10292). If you are interested in more sophisticated CUDA support, please check out the 2020.1 EAP build.
  • Google Test support:
    • False errors on Google Test v1.8.1 have been fixed (an error message was produced for INSTANTIATE_TEST_SUITE_P, see CPP-16301).
    • False positive inspection warnings for new MOCK_METHOD macro from Google Test v1.10.0 (CPP-18182).
  • Formatter improvements:
    • Reformat Code no longer breaks indentation in an enum when using a comment line (CPP-1836).
  • Several Clangd crashes were addressed.

The full release notes are available here.

The CLion 2020.1 EAP is now up and running. The first builds bring CUDA enhancements, Clang-cl support, the ability to debug customer targets, Data Flow Analysis rewritten on Clang, and much more. For more details please see this page.

Your CLion team
JetBrains
The Drive to Develop

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

4 Responses to CLion 2019.3.4 Bug-fix Update

  1. Taw says:

    Hi Anastasia,
    Does this fix update contains bug IDEA-231685? Or it happens only in 2020 EAP?
    Because I don’t want to update anything until this is fixed and merged with the rest of the projects (CLion, pycharm)
    Thanks

    • Taw says:

      Yep, it contains the horrible bug, I had to revert to CLion 2019.3.3. :(

    • Anastasia Kazakova says:

      As you can see in the ticket, it’s not yet resolve, so no fix is available for now. But we treat it seriously and consider fixing asap.

      • Taw says:

        Yes, I know that, but I was not sure in what CLion version did you merge with IDEA. So the bug happens in both 2019.3.4 and 2020.1 EAP.
        So 2019.3.3 is the last version without this bug.
        Thanks

Leave a Reply

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