- User Since
- Oct 24 2017, 1:28 PM (73 w, 4 d)
Jan 28 2019
Hello all, No I do not have dev account, you can associate this patch to
Jan 18 2019
- Fix testcase
Jan 14 2019
Well, it is true that this plugins dates from the Kdev4 days, and it is unmaintained. Anyways, with these patch, I correct the plugin to behave as described on
Jan 9 2019
Nov 29 2017
Well, I did some experiments and I think I got it why it was coded like that, and why the patch is correct (depending on what behavoiur was intended by original author):
Nov 28 2017
Yes, anyway I use that name because is consistent with the XDebugJob class (which uses the same mehtod name). Note that this path try to solve:
Well, I think that main source of problems is that Xdebug plugins maps the connection state to the debug state, and it generates a bunch of side effects if something get wrong. I think no other debug plugin do the same. So, for instance, if you do not have a connection it is necessary to set the status "manually" as I did in another patch.
As far I remember, the server will close even if they are listening connections, so next time we start xdebug, it will crash. It was mostly trial and error approach.
Oct 24 2017