Skip to content
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

xdebug not work #2112

Closed
AndreiiP opened this issue May 4, 2019 · 3 comments
Closed

xdebug not work #2112

AndreiiP opened this issue May 4, 2019 · 3 comments
Labels

Comments

@AndreiiP
Copy link

AndreiiP commented May 4, 2019

Info:

  • Docker version ($ docker --version): 17.05.0-ce, build 89658be
  • Laradock commit ($ git rev-parse HEAD):
  • System info (Mac, PC, Linux): Ubuntu
  • System info disto/version: 18.04

// place a code sample here

xdebug ini
xdebug.remote_host=host.docker.internal
xdebug.remote_connect_back=1
xdebug.remote_port=9000
xdebug.idekey=PHPSTORM

xdebug.remote_autostart=1
xdebug.remote_enable=1
xdebug.cli_color=1
xdebug.profiler_enable=0
xdebug.profiler_output_dir="~/xdebug/phpstorm/tmp/profiling"

xdebug.remote_handler=dbgp
xdebug.remote_mode=req

xdebug.var_display_max_children=-1
xdebug.var_display_max_data=-1
xdebug.var_display_max_depth=-1

settings php storm
http://i.imgur.com/9VKLXix.png

When I run the code, I get it
http://i.imgur.com/RmQ4wUn.png

A month ago, everything worked

@pricelessrabbit
Copy link

how do you use xdebug? are you listening for connections (via the green phone icon in xdebug) or are you debugging via the XDEBUG_SESSION_START parameter in the browser?
If you use the parameter it doesn't work anymore because of this modification
#2100

I submit a PR to fix the issue

you have also to set remote_autostart=0, otherwise xdebug set the idekey attribute to "PHPSTORM" and not to the numeric value passed by XDEBUG_SESSION_START

mouyong pushed a commit to mouyong/laradock that referenced this issue Aug 9, 2019
NetBT pushed a commit to NetBT/opdock that referenced this issue Jan 17, 2020
@stale
Copy link

stale bot commented Feb 2, 2020

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.

@stale stale bot added the Stale label Feb 2, 2020
@stale
Copy link

stale bot commented Feb 23, 2020

Hi again 👋 we would like to inform you that this issue has been automatically closed 🔒 because it had not recent activity during the stale period. We really really appreciate your contributions, and looking forward for more in the future 🎈.

@stale stale bot closed this as completed Feb 23, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

2 participants