-
Notifications
You must be signed in to change notification settings - Fork 3k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Segfault when resuming from xdebug breakpoint in PHPStorm (and maybe other places?) #4351
Comments
Same here. Happens when I try to resume from a triggered xdebug breakpoint using PHPStorm.
|
I got a second identical crash. I grow more certain that it is related to an exception (deadlock) in session callback. |
Same in HHVM 3.4.2. |
FWIW I 'moved' the sessions to Redis and this went away. (I didn't intend the sessions to be in the DB, it was a regression in a config file). I'm more or less certain that this was caused by an exception (deadlock due to galera cluster) in the db based session implementation. Most likely an/the exception is not expected in a registered session callback handler. |
|
happens in any project with any type of breakpoint |
Sounds like we have some consistent reports. The xdebug/phpstorm thing is worth looking into when we get some time -- the issue seems to happen with more than just that, but it sounds like a consistent repro. |
happens to me also on remote debugging using phpstorm. my steps are:
at this point hhvm is stopped and not responding anymore. |
Hello, I'm working on debugger integration in PhpStorm and I'll be happy to provide you any information that will help to fix the issue. So if you need any assistance feel free to contact me. |
I am also having this problem, with the same steps using phpstorm. |
@paulbiss do you know if anyone is actively working on xdebug? Might be useful to take up @SvetlanaZem's offer if someone is, though I suspect we don't have anyone with the spare time right now? |
@alexmalyshev is working on hphpd, and had been looking at Xdebug as a potential replacement. I think he handed off the Xdebug work to the IDE folks, but he may know who was looking at it most recently anyway. |
If they are useful, I have attached HHVM's xdebug logs to the PhpStorm issue WI-26478 (https://youtrack.jetbrains.com/issue/WI-26478). I think @SvetlanaZem believes this is an issue with HHVM. Let me know if there's anything you want me to test. |
There are three responses for a single "breakpoint_set" command in xdebug.log files provided by @RoyHP Anyway it looks like another problem, please let me know if I should create separate issue. |
@jwatzman Someone is reporting this issue is not only limited to PHPStorm, but also happening with MacGDBp. They are commenting on the issue I created with PHPStorm in my last comment. |
Issue is still there for HHVM 3.7.0. |
I can also confirm the issue:
happens after resuming from a breakpoint |
same here with HHVM 3.7.0/Nginx with PhpStorm EAP or 8.0.*
|
please see my colleague's comment about hhvm xdebug read buffer handling |
Can someone who was having this problem try it again with the latest nightly build of HHVM? #4488 has been fixed and I wonder if this is too. |
Leaving this open until confirmed fixed, but won't be personally working on it right now. |
The problem still exists for us when remote debugging to a Vagrant box:
Resuming from a breakpoint intermittently causes a segfault. |
Is anyone still seeing this? The recent work on xdebug for nuclide debugging support fixed a lot of hard to find bugs. |
Closing. Needs more info. (https://github.com/facebook/hhvm/wiki/Human-Timeouts) |
Here is the contents of the stacktrace:
This MAY have been caused by an exception in a registered callback for __SystemLib\SessionForwardingHandler->close()
The text was updated successfully, but these errors were encountered: