Unable to connect using VSCode

juber-nunes commented 3 years ago

The installation is done

I'm using laravel-s on a containerized environment.

zend_extension=yasd yasd.debug_mode=remote yasd.remote_host=127.0.0.1 yasd.remote_port=9000

but not connecting on VsCode

Originally posted by @juberjj in https://github.com/swoole/yasd/issues/78#issuecomment-760904975

sy-records commented 3 years ago

You need to set debug_mode as remote, not cmd

juber-nunes commented 3 years ago

Hi @sy-records

That's what've done

huanghantao commented 3 years ago

Can you use the following command to connect?

nc host.docker.internal 9003 -vv

huanghantao commented 3 years ago

And don't forget the -e option, for example:

php -e bin/index.php

juber-nunes commented 3 years ago

Port seems to be refusing connections, weird as I have it opened on firewall

huanghantao commented 3 years ago

By the way, yasd currently does not support remote_host using domain name. Maybe you should use IP instead.

huanghantao commented 3 years ago

Port seems to be refusing connections, weird as I have it opened on firewall

Has your IDE started listening? You can check the port.

juber-nunes commented 3 years ago

@huanghantao by having the ip set resolves the connection issue by running rc, I cann see connection opened and if I close it on IDE I get appropriate response, but still not debugging it

juber-nunes commented 3 years ago

on VSCode I have this

I'm using "laravels" to serve the application

huanghantao commented 3 years ago

Can you show me the contents of the terminal? There is no problem with your VS Code configuration.

juber-nunes commented 3 years ago

Sure. Just to let you know, it seems to connect as you can see "running" on editor call stack but it doesn't seem to hold it.

huanghantao commented 3 years ago

Have you set a breakpoint? Perhaps you can set a breakpoint in the entry file to test.

huanghantao commented 3 years ago

If the project paths of your virtual machine and your host do not match, you need to set path mapping, just like:

// virtual machine -> local
"pathMappings": {
  "/var/www": "${workspaceRoot}/www",
}

juber-nunes commented 3 years ago

I did indeed, also included "everything" just in case but I got nothing. I've done the same with sdebug and the only reason I got a little further was because of a flag "xdebug.remote_autostart=on"

huanghantao commented 3 years ago

I did indeed, also included "everything" just in case but I got nothing. I've done the same with sdebug and the only reason I got a little further was because of a flag "xdebug.remote_autostart=on"

yasd does not need to configure any Xdebug configuration items, just remote_host and remote_port

huanghantao commented 3 years ago

Can you configure the following configuration? After debugging, the debug.log file will be generated in the current directory, you can provide me with a look:

yasd.log_level=0

juber-nunes commented 3 years ago

which is great. :) . One step forward with pathmappings

juber-nunes commented 3 years ago

debug.log

breakpoint_list -i 1 179<?xml version="1.0" encoding="iso-8859-1"?>

breakpoint_list -i 2 179<?xml version="1.0" encoding="iso-8859-1"?>

breakpoint_list -i 3 179<?xml version="1.0" encoding="iso-8859-1"?>

breakpoint_list -i 4 179<?xml version="1.0" encoding="iso-8859-1"?>

breakpoint_list -i 5 179<?xml version="1.0" encoding="iso-8859-1"?>

breakpoint_set -i 6 -t line -f file:///engage-web/bootstrap/autoload.php -n 3 192<?xml version="1.0" encoding="iso-8859-1"?>

breakpoint_set -i 7 -t line -f file:///engage-web/app/Http/Controllers/Auth/ForgotPasswordController.php -n 45 192<?xml version="1.0" encoding="iso-8859-1"?>

breakpoint_set -i 8 -t line -f file:///engage-web/public/index.php -n 52 192<?xml version="1.0" encoding="iso-8859-1"?>

breakpoint_set -i 9 -t line -f file:///engage-web/app/Notifications/ResetPassword.php -n 42 192<?xml version="1.0" encoding="iso-8859-1"?>

breakpoint_list -i 10 180<?xml version="1.0" encoding="iso-8859-1"?>

breakpoint_list -i 11 180<?xml version="1.0" encoding="iso-8859-1"?>

run -i 12 286<?xml version="1.0" encoding="iso-8859-1"?>

286<?xml version="1.0" encoding="iso-8859-1"?>

1 286<?xml version="1.0" encoding="iso-8859-1"?>

juber-nunes commented 3 years ago

Removed the breakpoint from autoload and the error stopped. Went to the browser to capture other entrypoints but no luck

498<?xml version="1.0" encoding="iso-8859-1"?>