What exactly does "skipped breakpoint at ... because it happened inside debugger evaluation" mean?

Hi, this message is shown if debugger is stopped on a suspend all breakpoint and evaluates the code which hits another breakpoint. In your case most probably the breakpoint condition evaluation triggers another breakpoint.

Thanks. Though this make sense and probably the case in some scenarios, it doesn't look like it is the case for me.

I have a 'do while( true ) { receive(); }' loop where messages are received via tcp and few unconditional breakpoints in 'receive()'. From the status bar message these are being skipped. 'receive()' is not called from anywhere else.

Also I had a case where another breakpoint in a function called by 'receive()' was hit and the call stack indicated that a breakpoint in 'receive()' should have been hit before the one that was triggered.

If you can create a test case project I could have a look.

My plan is to try something more primitive (jdb?) and observe the wire protocol to see if I can get a sense of what is going on. Will update here. Thanks.

I have the same issue with a slightly complex conditional breakpoint.

All my breakpoints are 'Suspend All' so no thread can be running when my program is stopped (which I assume is a condition for the debugger to be 'evaluating' something)

I have a breakpoint with this condition which breaks correctly:

`value.getIdentifier().equals("Power")`

When I change the condition to this, it always fails with "skipped breakpoint at ... because it happened inside debugger evaluation":

`value.getIdentifier().equals("Power")&&((BooleanRegisterValue)value).getState()`

The method getState has a single statement returning a boolean field which has no breakpoint.

Also, this is in plain Java. No remote, Maven, or anything. (Ignoring the localhost debugging connection)

(IC-201.7846.76 running on JetBrains VM, my programming running on OpenJDK 11.0.7+10-post-Ubuntu-2ubuntu218.04)

The problem is described in IDEA-43728 and in the breakpoints documentation.

In short, to avoid it use suspend thread (not all) breakpoint policy.

(https://stackoverflow.com/questions/47866398/skipped-breakpoint-because-it-happened-inside-debugger-evaluation-intellij-ide/47884439#47884439)

I don't see the relevance. That thread is about the program suspending on a breakpoint but other threads running and skipping breakpoints. I'm having no such problem.

While "suspend all" breakpoint is evaluating its condition, it resumes all threads. During this other breakpoints may be hit (they will be skipped).

Switching to "suspend thread" resolves this by evaluating the condition only resuming one thread.

There's no thread to resume. The program is running from the start and skipping the breakpoint. Besides I already tried both (suspend thread is my default policy)

If it does not work with "suspend thread" breakpoints, please file a bug, we'll need more details. Thanks!

Unsure whether to post here or start a new thread. In my case I'm trying to set a breakpoint in a hascode/equals that I have overriden when stopped on a breakpoint and using evalute (alt-f8).

I get the message: “Skipped breakpoint at …. because it happened inside debugger evaluation”. This used to not be the case, I know this because I use this feature all the time. I'm using 2024.1.2#IU-241.17011.79.

Why would I ever want to skip such a breakpoint? 

I tried the suspend thread and made it default, also checked ‘Resume only the current thread’.

Bond Han are you sure it's the same? Because my usecase is this:

- put a breakpoint in the hashCode and equals of the parent of all my objects

- put a breakpoint on line: “someObject.getChildren().remove(selectedChild)”

- let the code stop on the breakpoint

- hit evaluate

- run “someObject.getChildren().remove(selectedChild)” in evaluate

Then the yellow message appears saying “because it happened inside debugger evaluation”. 

Is there a workaround for my issue?