CLion Debugger doesn't work. Will this ever change?

I'll repeat this post at least once per year, this is the 3dr year. CLion debugger (gdb/Linux) is still a major PITA, as quite often it gets stuck right in the middle of a debugging session, with a gdb process running at 100% CPU. It is still not possible to use CLion as a single IDE, you always have to keep another one around for such cases..

Chris

3 comments
Comment actions Permalink

Christian, we are very sorry for such an unpleasant experience. At the moment, we are preparing a number of fixes for the upcoming 2016.2 EAP builds. We encourage you to try them as soon as they announced.

0
Comment actions Permalink

just had another command timeout using the latest EAP. Also, sometimes rendering of local variables doesn't work

0
Comment actions Permalink

Christian,

 

Could you please enable debug log (add #com.jetbrains.cidr.execution.debugger option to Help | Debug Log Settings) and send logs (Help | Show Logs) to us after you encounter these problems again?
And of course it would be extremely helpful if you share some project example along with steps to reproduce, so we can try to repeat and investigate problem on our site.

Thank you!

0

Please sign in to leave a comment.