Clion debug12/20/2023 ![]() ![]() Let’s pick a test we want to debug, place a few breakpoints in the code, and click the gutter icon next to the test name: If we want to debug a test or target that doesn’t take input arguments, the quickest way is to use the gutter menu. You can set the appropriate toolchain by running rustup default. If you’re on MinGW64, it should be x86_64-pc-windows-gnu. For example, if you’re working on MinGW (32-bit), the default toolchain should be i686-pc-windows-gnu. Then, run rustup toolchain list and check the first line: it should be one of the gnu versions matching the bitness of the debugger. On Windows, go to Settings | Build, Execution, Deployment | Toolchain and set either Cygwin or MinGW as your working environment. If the indexing is finished and the Cargo tool window shows all the modules and targets of the workspace, you’re good to go. Before you beginįirst of all, make sure that your project is fully loaded. If you need more information at any point, please refer to the plugin’s Quick Start Guide and the Debug section in CLion’s web help. Debugging a Cargo Command configuration.We’ll start by diving right into a debug session to get a grounding in the basics, and then we’ll explore the debugger settings and additional options in detail. In this post, we’ll take a closer look at how the plugin cooperates with CLion when it comes to debugging your Rust applications. It’s been a while since we last dedicated a whole blog entry to IntelliJ Rust. ![]()
0 Comments
Leave a Reply.AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |