We’ve just rolled CLion 1.0.4 that fixes a very annoying issue with ‘Command timed out’ while debugging. You most probably experienced it if debug tool window kept showing “Collecting data…” forever for you. Or gdb ended with ‘Command timed out’ during the debug session.

We are sorry for the inconvenience. Thanks for you patience and we hope it’s resolved now with this update. Feel free to share the feedback with us.

The parser work is still in progress. So the current state is not ready for providing a point release. So most probably it will be ready for 1.1
Still some issues maybe included into upcoming 1.0.x updates.

I just had this exact problem for the first time while trying to use the 1.1 EAP version. All my debugging sessions in this and prior versions were successful up until this point, but now rolling back to using 1.0.5 is still showing the same thing.

Could you please collect debug logs (Help | Configure Debug Log | Add #com.jetbrains.cidr.execution.debugger) while starting a session and send to us (logs can be found in Help | Show Log) to clion-support at jetbrains.com? If you could also attach some sample project this would be great as well (however not necessary). This can help us a lot in investigation, thanks.

This issue still affects cLion 1.2; I was able to fix it by using the non-bundled gdb on a centos box. It looked like the issue there was that entries needed to be added to ~/.gdbinit:
set auto-load safe-path /
set libthread-db-search-path /lib64/

Without that, there were warnings about not being able to debug multithreaded applications, and I’d see commands time out.

It didn’t look like the bundled gdb reads ~/.gdbinit, so I had to use the non-bundled gdb at /usr/bin/gdb from within cLion as the final step.

We still need to check what’s going on there. We haven’t switched smth off intentionally. But maybe just some commands from .gdbinit are not applied by some reason. We are currently investigating the issue.

Could you please try the latest CLion 1.5 EAP build (https://confluence.jetbrains.com/display/CLION/Early+Access+Program) and if the problem is still there, share the code sample to reproduce the problem with us? We are currently working on the bunch of problems most likely causing the “time out” error. Some code sample to reproduce will be very useful.

My application is multithreaded + OpenCL (must not be important).
Debugging correctly stops on first breakpoint – but all other breakpoints are silently skipped.
If I disable first one breakpoint – debugging will be paused only on second breakpoint, and all other breakpoints will be skipped.