What to do if debugger doesn't work as expected? Follow
Please send us logs to investigate the problem. Do the following:
- go to Help | Debug Log Settings
- add #com.jetbrains.cidr.execution.debugger there
- reproduce the problem (mind, this step should happen after you added the settings above)
- collect debug logs, logs can be found in Help | Show Log in <File Manager>
- send logs to us via submitting a request here and attaching log files.
Note: Logs might contain private user's information (like file paths and names).
Update: If you have a timeout problem, you can also try and increase the timeout value.
Please sign in to leave a comment.
Recently we've published CLion 2016.2 EAP build, which includes major changes in GDB and LLDB drivers and addresses such problems as:
Please, find more details in our blog post.
This still happens with attach to process GDBs.
It will be a good idea to write exactly this mini-tutorial as it is in CLion.
For example there is no "Help|Show Log" option, but "Show Log in File Manager"
Tau, what is not clear from the instruction, except for the path to find logs in the menu (which differs for every platform, so I guess Show Log was enough to get it, but could extend)?
For example "Help | Configure Debug Log Settings" does not exist, looked for it for 30seconds, I searched it in another mensu, because I was expecting to start with "C" from "Configure". But in CLion it's "Debug Log Settings" :)
Thanks Tau. Seems the name in the menu changed after the article has been published. Updated here.
my debugger is not responding at all... impossible to work (see https://youtrack.jetbrains.com/issue/CPP-10071). Tried this to see what's happening in the log, but I can't find any useful info... any help would be much appreciated!
I am currently having the same problem with a Grails project i.e. "step over is treated as a step into".
The debugger steps into conditional blocks when it should not, even, if 1==2.