[BUG?] PHPstorm debugger stopping on disabled breakpoints, or breakpoints that removed.

So here the steps. 

You place breakpoint. Its perfectly working.

Then you removing that breakpoint, but next time debugger still stops at that point.

PHPStorm Version: 2017.1.2 

Debugger : Xdebug v2.4.0

PHP : v7.0.15

8 comments
Comment actions Permalink

It was difficult to find exact scenario when that happens , but i got it :)

So here the steps.

  1. Clicking Debug in PHPstorm. Session starts. (No breakpoint setted anywhere!)
  2. Placing breakpoint somewhere.
  3. Reloading page. After that we got redirected to phpstorm. Everything fine.
  4. Next , we clicking on "Resume Program Execution(F9)" From Debug Window , and immediately removing breakpoint. ( Important! . If we removing breakpoint a bit later (like 3-5 secs) after we clicked on "Resume Program Execution" , everything works properly as expected.)
  5. After that every time i reloading page , i got redirected to PHPStorm on same breakpoint. PHPStorm doesnt showing it, but from  logs i can see that xdebug didnt removed that breakpoint from list. ( See line 30 https://pastebin.com/sgUb3Lqx )
  6. And you wont remove it until you didnt destroy current xdebug session.
2
Comment actions Permalink

Do you remove those breakpoints while current debug session is active? Or you stopping the debug session, removing breakpoints & start it again?

Is it a local web server?

0
Comment actions Permalink

Its a local web server. And debug session is active when i try it. I don`t disabling it.

0
Avatar
Vladimir Luchansky
Comment actions Permalink

Hello,

To troubleshoot this, it would be necessary to configure the Xdebug log via https://xdebug.org/docs/all_settings#remote_log, restart your web server so it would propagate the changes of php.ini, reproduce the issue and attach the log output here (directly or via some service like pastebin).

0
Comment actions Permalink

Are you able to share a file/project where this can be reproduced?

0
Comment actions Permalink

It's a tough bug. I can reproduce it when I add a breakpoint to a line of code, and after finishing debugging and start working in another class and put a breakpoint in the new class, the debugger still stop at the pervious one.

0
Comment actions Permalink

It's filed here: https://youtrack.jetbrains.com/issue/WI-24557

Although, I use debugging in support purposes all the time, and have never seen this issue, so it must be something specific to the environment you use.

0

Please sign in to leave a comment.