Laravel project: Debug session was finished without being paused

Answered
Avatar
Abrcicbor
Created

In my Laravel project using PhpStorm (2018.1) I am not able to debug my session using xdebug (2.9.5). Any breakpoint gets ignored and session ends without being paused. If I set Break at first line in PHP scripts then session stops at index.php file. I am using Ubuntu 20.04.

PHP 7.4.5 (cli) (built: Apr 23 2020 08:10:29) ( NTS )
Copyright (c) The PHP Group
Zend Engine v3.4.0, Copyright (c) Zend Technologies
    with Xdebug v2.9.5, Copyright (c) 2002-2020, by Derick Rethans

This are my settings for xdebug in php.ini

[xdebug]
zend_extension = /opt/lampp/lib/php/extensions/no-debug-non-zts-20190902/xdebug.so
xdebug.remote_enable=1
xdebug.remote_port=9001
xdebug.remote_log="/tmp/xdebug.log"


I also have Xdebug helper extension in my Chromium but it seems to have the same effect with it enabled as well as disabled.
PhpStorm settings:




Votes

0

Share

6 comments
Avatar
Eugene Morozov
Created

You seemed to have missed my question on SO, so sorry for asking again, but:

Try adding a simple assignment statement to the beginning of this file (right under the PHP tag) and set a breakpoint there, would it stop on this breakpoint?

I forgot about namespaces in this question, so yes, after the tag and the namespace declaration. Also, please let it be something like this, with the breakpoint on the assignment, to avoid optimizing it as an unused assignment statement.

$myVar = 1;
print $myVar;
0
Avatar
Abrcicbor
Created

Thanks for taking interest, i did as you suggested, still the same Debug session was finished without being paused message.

Here is the log if it means anything: https://pastebin.ubuntu.com/p/DksQJthMj3/

Thanks again.

I would like to know is this about some misconfiguration, is it about my project, OS, php/xdebug versions....? Not sure in which direction to look anymore.

I would assume that since index.php is hit, if i check Break at first line in PHP scripts, that everything is okay from xdebug/PhpStorm configuration part?!

0
Avatar
Eugene Morozov
Created

I compared the log to mine, and it seems that PhpStorm stops sending Xdebug any commands, so it might be something on our side.

Please add #com.jetbrains.php.debug to Help | Diagnostic Tools | Debug Log Settings, restart PhpStorm, initiate a debug session and then upload both the Xdebug and idea.log.

Probably it makes sense to attach the logs within an issue on our tracker, as I think I'd have to ask the devs for help anyways: https://youtrack.jetbrains.com/newIssue?project=WI

0
Avatar
Andriy Bazanov
Created

>In my Laravel project using PhpStorm (2018.1) 

Now it triggered...

Is that a correct version? 2018.1?

If so -- you are using Xdebug 2.9.5. You need PhpStorm 2018.3 or newer if you want to work with Xdebug 2.7 or newer. This is due to changes in Xdebug protocol (https://youtrack.jetbrains.com/issue/WI-43622).

Your version (well, 2018.2 and older) may only work with Xdebug 2.6.x or older.

1
Avatar
Abrcicbor
Created

I hope that I didn't miss anything.
idea.log: https://pastebin.ubuntu.com/p/TqW69SwZft/
xdebug.log: https://pastebin.ubuntu.com/p/9J4kB7gfBy/

0
Avatar
Abrcicbor
Created

After updating to PhpStorm 2020.1 it start working.

0

Please sign in to leave a comment.