Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Already on GitHub? Sign in to your account

Another crash #71

Closed
gdance opened this Issue Apr 6, 2013 · 5 comments

Comments

Projects
None yet
4 participants

gdance commented Apr 6, 2013

Hey,

I was just debugging something again and got this crash:

Waiting for a connection (Ctrl-C to cancel, this message will self-destruct in  20  seconds...)
E89: No write since last change for buffer 20 (add ! to override)
Traceback (most recent call last):
  File "<string>", line 1, in <module>
  File "/Users/gdance/.vim/bundle/vdebug/plugin/python/start_vdebug.py", line 31, in run
    self.runner.run()
  File "/Users/gdance/.vim/bundle/vdebug/plugin/python/vdebug/runner.py", line 156, in run
    self.open()
  File "/Users/gdance/.vim/bundle/vdebug/plugin/python/vdebug/runner.py", line 46, in open
    self.ui.open()
  File "/Users/gdance/.vim/bundle/vdebug/plugin/python/vdebug/ui/vimui.py", line 62, in open
    logwin))
  File "/Users/gdance/.vim/bundle/vdebug/plugin/python/vdebug/log.py", line 112, in set_logger
    cls.loggers[k].shutdown()
  File "/Users/gdance/.vim/bundle/vdebug/plugin/python/vdebug/log.py", line 50, in shutdown
    self.window.destroy()
  File "/Users/gdance/.vim/bundle/vdebug/plugin/python/vdebug/ui/vimui.py", line 335, in destroy
    self.command('bwipeout ' + self.name)
  File "/Users/gdance/.vim/bundle/vdebug/plugin/python/vdebug/ui/vimui.py", line 346, in command
    vim.command(cmd)
vim.error

Before that I had tried to start the debugger when I had not enabled all the xdebug stuff in Google Chrome and it gave an error and I had to close all the debugging windows manually and one of the windows kept showing up again after I had closed it.

Then I tried running it again and it crashed.

Owner

joonty commented Apr 8, 2013

Can you let me know which version of Vdebug you're using? There's a VERSION file in the root of the directory.

Thanks

Contributor

Chronial commented Apr 18, 2013

This might be fixed by #76

Owner

joonty commented May 10, 2013

Hi @gdance have you seen this issue since you reported it?

Thanks

gdance commented May 11, 2013

Hey guys! I haven't actually been debugging that much but I haven't ran into that many issues recently. I will let you know if I notice anymore problems.

Collaborator

qstrahl commented May 11, 2013

Sounds like case closed to me. Reopen the issue if it comes up again.

@qstrahl qstrahl closed this May 11, 2013

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment