What to do if debugger doesn't work as expected?

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.

11 comments
Comment actions Permalink

Recently we've published CLion 2016.2 EAP build, which includes major changes in GDB and LLDB drivers and addresses such problems as:

  1. Command timeouts.
  2. Stepping problems.
  3. Debugger performance issues.

Please, find more details in our blog post.

0
Comment actions Permalink

This still happens with attach to process GDBs.

0
Comment actions Permalink

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"

0
Comment actions Permalink

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)?

0
Comment actions Permalink

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" :)

0
Comment actions Permalink

Thanks Tau. Seems the name in the menu changed after the article has been published. Updated here.

Edited by Anastasia Kazakova
0
Comment actions Permalink

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!

0
Comment actions Permalink

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.

Edited by Anthony Mc Egan
0
Comment actions Permalink

Same  issue with intellij 2018.3, I tried with jdk 1.8u202 1.8u201 1.8u192

Edited by Marco Scarpa
0
Comment actions Permalink

This happens with IntelliJ Ultimate 2019 version as well.I find that it happens for a maven configuration. If I happen to run the spring boot app with Spring boot configuration (not as MAVEN ) then it works fine. But I wanted to make sure that I can run as maven configuration since that is the one I will use in my container.  Is there a solution to it. ?

0
Comment actions Permalink

Please mind this is a FAQ on CLion IDE. Contact IntelliJ IDEA support for issues in it. They will be glad to help. 

0

Please sign in to leave a comment.

Have more questions?

Submit a request