Kind of. After connecting to the gdb server, CLion's GDB client usually sends some commands (IIRC start) that will not return a proper response because the serv

Kind of. After connecting to the gdb server, CLion's GDB client usually sends some commands (IIRC start) that will not return a proper response because the server does not support it. Our solution was writing a wrapper to the GDB's machine interface that just ate the problematic commands that are being sent and from then on it works. I don't know if it has been fixed, this is the most recent article i found and it's been a while since I last tried to tackle this problem (previous job). https://blog.jetbrains.com/clion/2017/12/clion-for-embedded-development-part-ii/ https://blog.jetbrains.com/clion/2017/12/clion-for-embedded-...