Debug

C++ language news, sanitizers, C++20 concepts, parallel STL algorithms, C++ tools releases, and interview with Bjarne Stroustrup

The C++ ecosystem is evolving, and so too is our cross-platform C/C++ IDE. CLion 2021.2 can help you by protecting your code from typical C++ memory safety issues, simplifying your build configurations, and making debugging easier and more effective.

Today we have Greg Law with us. In this guest blog post, Greg will share a few top tips for debugging C++ code. Greg (@gregthelaw) is the co-founder and CEO at Undo. He is a programmer at heart, but likes to keep one foot in the software world and one in the business world. Greg finds it particularly rewarding to turn innovative software technology into real business develo

The CLion 2021.2 Early Access Program was recently launched. Did you manage to try out the new Load CMake Presets feature? Or did you play with Cling, an interactive C++ interpreter now supported in CLion? We really hope you managed to catch a few dangling pointers or references with the help of recently introduced Lifetimes analysis. Today we are happy to announce the second EAP build (212.3724.

This if the third and final part of our Advanced Debugger series. If you haven't seen them, do catch: "Part 1: Suspended" and "Part 2: Dynamic" As well as the earlier, "Debugging Fundamentals" video. In this video we start by looking a direct access to the GDB or LLDB terminal, as well as running commands on start-up using .gdbinit or .lldbinit, then look at attaching to external process

Following up on "Part 1: Suspended", of our Advanced Debugger series, Part 2 focuses on the dynamic part of working with breakpoints, watchpoints and setting the execution point. Because this an advanced series, we look beyond simply setting and removing breakpoints, and take a look at the different types of breakpoints we support, as well as all the options along with them. In many cases your bre

Back in October of last year I wrote "CLion Debugging – Part 1: Fundamentals", to introduce the everyday debugging features in CLion. It was "Part 1", because the promise was that I would follow up with a "Part 2", covering more advanced features. One thing you should never do is call something "Part 1" before you've written later parts! Part 2 has been a lo

The new CLion 2021.1 EAP build (211.6432.9) is now available. You can get it from our website, via the Toolbox App, or as a snap package (if you are using Ubuntu). Note that if you are on macOS, there is a separate build for Apple Silicon (M1 chip). DOWNLOAD CLION 2021.1 EAP More MISRA C and C++ checks We continue our work on extending the list of supported checks. You can find the current list of

This version is focused on the debugging experience and on the flexibility of the unit testing integration. Embedded developers will find support for the first collection of MISRA checks. CLion 2020.3 also introduces a variety of IDE functions tuned specifically for working with Qt code.

CLion 2020.3 has reached Beta! Build 203.5981.40 is available from our website, via the Toolbox App, or as a snap package (for Ubuntu). DOWNLOAD CLION 2020.3 EAP The CLion 2020.3 EAP has already introduced a couple of performance-enhancing features to the debugger: A new Set Execution Point action Ability to debug Core Dumps And there’s even more in the Beta! Ability to run and debug with

In the previous 2020.3 EAP build we were focused on giving run/debug configurations and CMake profiles more flexibility in CLion, and at the same time we introduced a bundled tool for collaborative development and pair programming. In this EAP update we are adding one of the most long-awaited features in debugger – postmortem debug with a core file! Build 203.5600.25 is available from our website,

An important part of writing code is debugging. Despite the name this is not limited to just finding bugs in our code, but can help us to understand what the code is actually doing at runtime - often in a specific environment. While it's possible to do this to some extent using, so-called, "printf-debugging" (inserting code to write out messages and values to the console or a log file),