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

Error starting Vdebug: <class 'pynvim.api.common.NvimError'> #494

Closed
stephenplatz opened this issue Dec 2, 2020 · 9 comments
Closed

Error starting Vdebug: <class 'pynvim.api.common.NvimError'> #494

stephenplatz opened this issue Dec 2, 2020 · 9 comments

Comments

@stephenplatz
Copy link

I've already looked at #487, #485 and #486. I just pulled f61a967, but it's frankly been a while since I've updated. I can't start a debugging session at all, even after starting vim again.

NVIM v0.3.8

@lucc
Copy link
Contributor

lucc commented Dec 2, 2020

Can you post the full stack trace?

@stephenplatz
Copy link
Author

I guess I'm not sure how to provide something useful, I don't think you're looking for the vdebug logs.

@lucc
Copy link
Contributor

lucc commented Dec 2, 2020

I was hoping for a python stack trace that belongs to your headline for this issue. <class 'pynvim.api.common.NvimError'> looks like the type of an exception that I assumed was thrown.

Maybe you can also give exact steps what to do to reproduce this (php ini setting for xdebug, nvim command line, steps you perform).

@stephenplatz
Copy link
Author

stephenplatz commented Dec 2, 2020

I'd be happy to add a python stack trace here, but the error above is just appearing in my editor.

My php.ini simply has these settings:

xdebug.max_nesting_level = 256
xdebug.show_exception_trace = 0
xdebug.collect_params = 0
xdebug.remote_enable = 1
xdebug.remote_autostart = 0
xdebug.remote_host = ${LANDO_HOST_IP}
xdebug.remote_log = /tmp/xdebug.log

I'm using vdebug in the regular way I've always done, in this case I set a couple of breakpoints, hit <F5> and wait for the debugger. It appears that when a connection is made, the above error is thrown. What's the best way to get a stack trace?

@lucc
Copy link
Contributor

lucc commented Dec 2, 2020

You can check :help VdebugLogWindow and help VdebugOptions-debug_file.

I will try to reproduce tomorrow (at my work computer).

@stephenplatz
Copy link
Author

The log window opens when the error occurs without any additional information, it's completely empty. I was going to provide the log output above, but thought that it wouldn't be helpful. I'll provide a log here, there doesn't seem to be much in it, log level 2:

  • [Debug] {Wed 02 2020 14:05:29} keymapper: reload_keys
  • [Debug] {Wed 02 2020 14:05:29} Closing the socket
  • [Debug] {Wed 02 2020 14:05:29} Closing the socket
  • [Debug] {Wed 02 2020 14:05:29} Started
  • [Debug] {Wed 02 2020 14:05:29} Listening on port 9000
  • [Debug] {Wed 02 2020 14:05:32} Stopping server
  • [Debug] {Wed 02 2020 14:05:32} Finishing socket server
  • [Info] {Wed 02 2020 14:05:32} Vdebug stopped waiting for a connection
  • [Debug] {Wed 02 2020 14:05:32} keymapper: reload_keys
  • [Debug] {Wed 02 2020 14:05:33} Creating hidden buffer: [' 11000 | True | line | /home/steve/Applications/passtab-visitor-management/sites/all/modules/contrib/agreement/agreement.module:1217']
  • [Debug] {Wed 02 2020 14:05:33} Creating hidden buffer: []
  • [Debug] {Wed 02 2020 14:05:33} Creating hidden buffer: []
  • [Debug] {Wed 02 2020 14:05:33} Creating hidden buffer: []
  • [Debug] {Wed 02 2020 14:05:33} Creating hidden buffer: []
  • [Debug] {Wed 02 2020 14:05:33} Creating hidden buffer: []

Here's a screenshot for what it's worth:

Screenshot_2020-12-02_14-05-08

@Mte90
Copy link

Mte90 commented Dec 15, 2020

I think that is the same of #403

@Mte90
Copy link

Mte90 commented Dec 15, 2020

@stephenplatz
Copy link
Author

Upgrading my Neovim to v0.4.4 solved this and other issues for me.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants