Xdebug, Lando, Drupal 8
Hi folks,
I'm trying to get xdebug working with phpstorm (2018.1) on a Lando Drupal 8 setup. For some reason, I can't seem to get phpstorm to notice any incoming xdebug requests. I followed the instructions at https://docs.devwithlando.io/guides/lando-phpstorm.html which seem pretty straightforward. Is anyone using anything like this?
I am using xdebug helper in Chrome also.
thanks
Selwyn
Here are some outputs from the php in the lando container.
$ lando php -m | grep xdebug
xdebug
$ lando php -i | grep xdebug
/usr/local/etc/php/conf.d/docker-php-ext-xdebug.ini,
xdebug
xdebug support => enabled
xdebug.auto_trace => Off => Off
xdebug.cli_color => 0 => 0
xdebug.collect_assignments => Off => Off
xdebug.collect_includes => On => On
xdebug.collect_params => 0 => 0
xdebug.collect_return => Off => Off
xdebug.collect_vars => Off => Off
xdebug.coverage_enable => On => On
xdebug.default_enable => On => On
xdebug.dump.COOKIE => no value => no value
xdebug.dump.ENV => no value => no value
xdebug.dump.FILES => no value => no value
xdebug.dump.GET => no value => no value
xdebug.dump.POST => no value => no value
xdebug.dump.REQUEST => no value => no value
xdebug.dump.SERVER => no value => no value
xdebug.dump.SESSION => no value => no value
xdebug.dump_globals => On => On
xdebug.dump_once => On => On
xdebug.dump_undefined => Off => Off
xdebug.extended_info => On => On
xdebug.file_link_format => no value => no value
xdebug.filename_format => no value => no value
xdebug.force_display_errors => Off => Off
xdebug.force_error_reporting => 0 => 0
xdebug.gc_stats_enable => Off => Off
xdebug.gc_stats_output_dir => /tmp => /tmp
xdebug.gc_stats_output_name => gcstats.%p => gcstats.%p
xdebug.halt_level => 0 => 0
xdebug.idekey => no value => no value
xdebug.max_nesting_level => 512 => 512
xdebug.max_stack_frames => -1 => -1
xdebug.overload_var_dump => 2 => 2
xdebug.profiler_aggregate => Off => Off
xdebug.profiler_append => Off => Off
xdebug.profiler_enable => Off => Off
xdebug.profiler_enable_trigger => Off => Off
xdebug.profiler_enable_trigger_value => no value => no value
xdebug.profiler_output_dir => /tmp => /tmp
xdebug.profiler_output_name => cachegrind.out.%p => cachegrind.out.%p
xdebug.remote_addr_header => no value => no value
xdebug.remote_autostart => On => On
xdebug.remote_connect_back => Off => Off
xdebug.remote_cookie_expire_time => 3600 => 3600
xdebug.remote_enable => On => Off
xdebug.remote_handler => dbgp => dbgp
xdebug.remote_host => host.docker.internal => localhost
xdebug.remote_log => no value => no value
xdebug.remote_mode => req => req
xdebug.remote_port => 9000 => 9000
xdebug.remote_timeout => 200 => 200
xdebug.scream => Off => Off
xdebug.show_error_trace => Off => Off
xdebug.show_exception_trace => Off => Off
xdebug.show_local_vars => Off => Off
xdebug.show_mem_delta => Off => Off
xdebug.trace_enable_trigger => Off => Off
xdebug.trace_enable_trigger_value => no value => no value
xdebug.trace_format => 0 => 0
xdebug.trace_options => 0 => 0
xdebug.trace_output_dir => /tmp => /tmp
xdebug.trace_output_name => trace.%c => trace.%c
xdebug.var_display_max_children => 128 => 128
xdebug.var_display_max_data => 512 => 512
xdebug.var_display_max_depth => 3 => 3
Please sign in to leave a comment.
I have uninstalled and reinstalled Docker, Phpstorm and Lando and upgraded to the 2018.3 phpstorm. I've also removed my .idea directory in two projects and recreated them. I think the problem is that phpstorm sees the container but for some reason, it reports that the Debugger is not installed.
Jetbrains techie suggested I try https://blog.jetbrains.com/phpstorm/2018/08/quickstart-with-docker-in-phpstorm/ but no luck. Suggestions welcome.
We're working on the issue in a support ticket, probably will post a recap when it's solved.
Turns out that the cause was another process had the port 9000 already captured so PHPStorm couldn't find it.
I wrote it up at https://www.austinprogressivecalendar.com/blog/debugging-drupal8-phpstorm-and-lando-your-mac