CLion 2018.2 EAP: fixes for LLDB and C++ code analysis


A new CLion 2018.2 EAP (build 182.3208.14) is now available! A patch-update will be available shortly in case you are using the previous EAP build. You can also update via Toolbox app or snap packages (in case of Ubuntu). No license is required and the build is free to use, but it will expire within 30 days of the build date.

Download CLion 2018.2 EAP

Debugger: LLDB

We’ve bundled LLDB 6.0 on Linux and macOS. Besides, for LLDB case we’ve fixed an issue when certain commands in the LLDB console were breaking the IDE’s integration (CPP-11379).

C++ support

Intention that simplifies the code was improved and now produces more accurate code in case of pointers:
Other fixes include:

  • Incorrect warning “Variable might not have been initialized” was fixed for typedef array case (CPP-12444).
  • DFA didn’t handle overloaded operators like = and += in try section (CPP-11843).
  • Incorrect warning about “Unreachable code” in some cases (CPP-11838).

Full release notes are available by the link.

Your CLion Team
The Drive to Develop

This entry was posted in Early Access Preview and tagged , , . Bookmark the permalink.

8 Responses to CLion 2018.2 EAP: fixes for LLDB and C++ code analysis

  1. Martin Pecka says:

    The full release notes are kind of missing all CPP-* bugs.

    • Anastasia Kazakova says:

      There is a link in the beginning, right before the table on that page, to CPP-* issues. Unfortunately, due to some technical issues there were not present in the table. So we’d just added a direct link.

  2. NBlizz says:

    Can I use LLDB on Windows through WSL?

  3. mbalabin says:

    It is great to see that debugging fixes regularly make their way into releases. Debugging experience is a crucial part of any IDE. Good work!

    I want to draw your attention to two extremely annoying debugger bugs CPP-12472 and CPP-7276. Pretty-printing of variables does not work if a variable is a reference or a pointer. In a typical scenario you pass a std::vector parameter to a function as a const reference and… you can not see the contents of a parameter when debugging. Both LLDB and GDB seem to be affected. In my opinion it is currently the most noticeable debugger issue.

  4. Jonatan Wallmander says:

    Is compilation with CLang and debugging with LLDB on Windows on the roadmap?

    • Jonatan Wallmander says:

      Or debugging with CDB (Windows’ equivalent to GDB, a CLI debugger available through the Windows SDK)?
      Right now this is stopping me from evaluating properly as we build for Linux and Windows… :)

    • Anastasia Kazakova says:

      Clang is available on all the platforms. For Windows you have to install it via MinGW/MinGW-w64 or Cygwin.
      LLDB on Windows might be available later this year.
      Regarding the MSVC-compliant debugger (as the Microsoft debugger a proprietary one), we are currently working on some equivalent debugger, but I can’t promise you anything here. We are currently investigating the options.

Leave a Reply

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