![]() ![]() I confirmed that running a version of lldb outside of clion works correctly with the same binaries. For example, if you’re working on MinGW (32-bit), the default toolchain should be i686-pc-windows-gnu. Also, any crashes in the library just show up in the debugger in the main executable as if it was a crash in any old library that was not compiled with debug symbols. Then, run rustup toolchain list and check the first line: it should be one of the gnu versions matching the bitness of the debugger. So now it is not able to load any symbols from my library. This isn't the first time that I've added code like this in the main executable but somehow it hit some sort of tipping point yesterday in clion where it can't keep track of symbols in the library anymore. That is, just sharing a few more utility cpp/h files in both the executable and the library. I'm sure I'm getting something simple wrong, but whenever I try to debug a C program in CLion the debugger console pops up and says that it's running my executable, but there is never any output and I cannot interact with my program. Back in October of last year I wrote 'CLion Debugging Part 1: Fundamentals', to introduce the everyday debugging features in CLion. Bazel Google Compatible with CLion Overview Versions Reviews Bazel support for CLion. Im trying to use the CMake support to build the example GuiAppExample from the documentation for setting up CMake to create JUCE projects. The main executable loads and runs this library. Im pretty new to building on windows and have just spent my first day banging my head around trying to get CMake/CLion workingso bear with me. Here you go Now you can give input from the text file while debugging the code. Then check the 'Redirect input from' box and select the input file path and click 'OK'. Not a great solution for me but at least I can do basic debugging at the moment without resorting to something even worse than clion like straight lldb or some other nonsense.įor me the issue seemed to start to happen after I added more shared code that is also compiled in a loaded library into the main executable as well. Image of debug setting window Click the setting icon in the debug console (on upper left corner) to open the setting of debugging. After much desperation the "fix" for me was changing clion debugging settings to use gdb rather than the embedded lldb one.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |