CLion 2019.3 EAP: Debugger Improvements
A new CLion 2019.3 EAP (build 193.4386.19) is now available! Get it from our website, via the Toolbox App, or as a snap package (if you are using Ubuntu). A patch-update for those using the previous EAP build will be available shortly.
In this quality-targeted release, we work a lot on polishing CLion’s support for debuggers. As you know, we support two back-ends, LLDB and GDB. This build brings some long-awaited improvements and fixes for both.
LLDB: better pretty printers are in use
In the previous EAP build, we updated the bundled LLDB on macOS and Linux to v9.0. Now, we’ve cleaned the incorrectly working pretty printers for LLDB, fixing a whole set of related issues, which you can find linked to the parent ticket CPP-17548.
From the tables below, you can see that on macOS, libc++ is handled much better than libstdcxx for now:
GDB: read .gdbinit from the project root
Quite often you need to tune the debugger behavior via passing some commands and options in a .gdbinit file. Previously, CLion always read this file from the user’s home directory, which definitely was not very convenient and could cause conflicts. Now, CLion supports reading the .gdbinit file from the project root directory. This means you can customize your GDB experience on a per-project basis.
Note that to enable this behavior, you have to explicitly allow it in your home .gdbinit file, either globally or for a particular project. For the exact commands, see this.
By the way, a similar feature for LLDB is currently in development as well. Stay tuned!
Improvements from the IntelliJ Platform
There are also more enhancements in CLion coming from the IntelliJ Platform:
- We’ve updated the Database support bundled into CLion with initial support for MongoDB.
- We’ve fixed the issue with project opening on macOS 10.15 Catalina (JBR-1721).
Read more details in this blog post.
The full release notes are available here.
Your CLion Team
The Drive to Develop