![]() It would be better with a 'classic' script option, allowing you to override the default connection procedure. I tried to use that to load the binary, but I did not get that to work. gbinit will run before the 'target remote' from the plugin is launched. To me it seems not so far from working and the Rust support in CLion looks promising (perhaps the best amongst RustDT (not supported), and vscode (RLS based)). Symbol file:/home/pln/CLionProjects/rtfm-app/target/thumbv7em-none-eabihf/debug/examples/bare0 Arch linux with the CLion December 26 build. I'm on the latest nightly xargo/cargo and nightly rustup channel. Watching local (stack) as well as static (heap) variables always work.When they work, they are also updated in the source file. Setting breakpoints in the gdb console works fine. Breakpoints do not work, setting them in the IDE has no effect, stepping works and even (surprisingly) run to line.(I had to use the pause and in the gdb console load it, the file has the right path, so it loads correctly) I'm experimenting with debugging Rust on embedded (Nucleo STM32F401re) using openocd and arm-none-eabi-gdb. It looks like one user, has attempted this as well: Viewing / stepping through the Rust sourceĭoes anyone have any ideas on how to improve this?.The following things don't work at the moment: If a binary has already been loaded through gdb from the command line, CLion is able to connect and run the binary remotely, and pausing will pause the microcontroller and show disassembly in the CLion window. Let (mut delay, mut leds): (Delay, Leds) = aux5::init() ĬLion supports a Remote Debug run configuration, which I've so far configured like (testing in CLion 2018.1.6 on macOS): The sample program I am trying to load is from an LED routlette example: #! I've been following excellent discovery blog, where he describes how to debug an STM32 binary using gdb from the command line through openocd, and that works great:įor increased productivity, I'd like to debug natively within the CLion IDE. I don't know why, but switching the toolchain to msvc worked.I'm trying to debug an ARM binary running on a STM32F3DISCOVERY board using CLion + IntelliJ Rust. (As I said the program might be written very badly, as I am a beginner, but it works. U can also hit me up on discord, just tell me and I provide my username. Visual Studio 2022 and C++ debugs completely fineĪny questions? Let me know. I am no Rust expert, more a beginner but I am completely sure I never had those problems on my old Rig.ĭo you think it might have to do with my windows language settings? I am a german native and changed everything to English, maybe something broke the encoding or such? But I never had problems in other programs so idk. Here you can see my encoding config: when I changed everything to UTF-8 it did not work.Here you can see my debugger settings: I will get this error if I place the breakpoint next to it: Or when initializing an int like : let k = 2 Sometimes I get the following error when starting the debugger: .$GDBCommandException: Undefined item: "UTF-8". Already reinstalled CLion and Rust 3 times. My Problem now is, that my debugger seems a bit wonky? The program itself does run perfectly fine, with no errors nothing, simply the debugger makes problems. Hello, I build a new Rig and switched to Win11. We'll do our best to keep these links up to date, but if we fall behind please don't hesitate to shoot us a modmail. This is not an official Rust forum, and cannot fulfill feature requests. Err on the side of giving others the benefit of the doubt.Īvoid re-treading topics that have been long-settled or utterly exhausted. Please create a read-only mirror and link that instead.Ī programming language is rarely worth getting worked up over.īe charitable in intent. If criticizing a project on GitHub, you may not link directly to the project's issue tracker. Post titles should include useful context.įor Rust questions, use the stickied Q&A thread.Īrts-and-crafts posts are permitted on weekends.Ĭriticism is encouraged, though it must be constructive, useful and actionable. For content that does not, use a text post to explain its relevance. Posts must reference Rust or relate to things using Rust. We observe the Rust Project Code of Conduct. ![]() Strive to treat others with respect, patience, kindness, and empathy. Please read The Rust Community Code of Conduct The Rust Programming LanguageĪ place for all things related to the Rust programming language-an open-source systems language that emphasizes performance, reliability, and productivity.
0 Comments
Leave a Reply. |