The first couple of times I tried to submit/report this issue the website showed an error message saying something along the lines of "Invalid Secutiry Marker" (translated). All of my input was lost so I decided to create the issue with minimal info first and then add information afterwards to make sure I don't have to type out all of the info repeatedly.

The issue does not seem to occur with Xdebug vesion 2.8.1. Also after enabling 2.8.1 and after that reenabling 2.9.3 the issue happened at other breakpoints.

The image file I've attached in the main section of the bug report demonstrates clearly what happens.

I should mention that I'm using Xdebug through its PhpStorm integration but changing to different PhpStorm versions (years apart) makes no difference.

I understand that reproducing/fixing this issue might be difficult but it does not seem to happen with Xdebug version 2.8.1. Hopefully others can provide more input. My best guess by far is that it might have to do with the breakpoint resolve feature introduced with Xdebug 2.8.

Please follow the instructions on how to report a bug as is described here: https://xdebug.org/reporting-bugs

In particular, the section on "Step Debugger Bugs" at https://xdebug.org/reporting-bugs#step-debugger — it is vital that I can reproduce this myself.

Hi,

I've asked for follow up information three weeks ago. If this does not get provided soon, I will close this ticket out.

cheers,
Derick

Hi,

sorry for the delayed response. I will follow up on this before Tuesday next week.

Best regards,
Milen

Go ahead and close this. Currently I have no time to test and evaluate this. When I have spare time I will provide the required data and it may be reopened.

OK. Thanks.

Please open a new issue with the new information, as this bug system doesn't allow you to reopen a closed bug.

cheers,
Derick