You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
AttributeError: Debugger instance has no attribute 'bend' #3
I got an error message that I dismissed by accident without being able to read. Now I cannot :Dbg quit -- I get this traceback:
Traceback (most recent call last):
File "<string>", line 1, in <module>
File "/home/mg/.vim/plugin/vim_debug/commands.py", line 44, in debugger_cmd
cmd['function'](*args)
File "/home/mg/.vim/plugin/vim_debug/new_debugger.py", line 187, in quit
self.bend.close()
AttributeError: Debugger instance has no attribute 'bend'
":Dbg ." now doesn't work either -- prints the usage message -- so there's no obvious way to debug anything without restarting vim.
I think I ran into this by syncing my .vimrc and .vim from another workstation where I had previously done a full proper vim-debug install. On my other workstation, I had enough to try to run, but I had not installed dbgp.
I am also running into this issue. I am on Snow Leopard and MacVim, I installed both https://github.com/jabapyth/pydbgp and this project using sudo python setup.py install, and now am running exactly mgedmin's problem described above. :py import dbgp seems to work fine though.
Traceback (most recent call last):
File "<string>", line 1, in <module>
File "/usr/local/lib/python2.7/dist-packages/vim_debug/commands.py", line 44, in debugger_
cmd
cmd['function'](*args)
TypeError: quit() takes exactly 1 argument (2 given)
Traceback (most recent call last):
File "<string>", line 1, in <module>
File "/usr/local/lib/python2.7/dist-packages/vim_debug/commands.py", line 44, in debugger_
cmd
cmd['function'](*args)
File "/usr/local/lib/python2.7/dist-packages/vim_debug/new_debugger.py", line 186, in quit
self.bend.close()
AttributeError: Debugger instance has no attribute 'bend'
So, I tried to find out what was happening in the code and looks like pydbgp.py couldn't initialise due a environment variable that it didn't recognised.
After running the following command(e.g. setting the required environment variables), it worked:
Activity
jaredly commentedon Jul 16, 2010
well that's what you get for fooling around ;) I'll look into it.
mgedmin commentedon Jul 16, 2010
Apparently this happens when there's no pydbgp.py on the path.
slestak commentedon Jul 25, 2010
I think I ran into this by syncing my .vimrc and .vim from another workstation where I had previously done a full proper vim-debug install. On my other workstation, I had enough to try to run, but I had not installed dbgp.
jaredly commentedon Jul 27, 2010
Ok. I think I understand what's going on.
ceptorial commentedon Aug 2, 2011
I am also running into this issue. I am on Snow Leopard and MacVim, I installed both https://github.com/jabapyth/pydbgp and this project using sudo python setup.py install, and now am running exactly mgedmin's problem described above. :py import dbgp seems to work fine though.
SebastianWendel commentedon Nov 26, 2012
Hi Jared,
is there any change with that issue?
Im also having the same problem, i run debian vim+python and used https://github.com/fisadev/fisa-vim-config
Installed everything successfully, but no change.
Any Idea? Help would be great.
Thanks,
Sebastian
SebastianWendel commentedon Nov 26, 2012
Something more:
the vimrc uses vundler, what i think is not the problem, but it uses a workaround:
The keyboard bindings also look good.
Tomorrow i gonna try the manual installation and let you know if it helped.
Greetings,
Sebastian
jaredly commentedon Nov 26, 2012
Great, I'll have a closer look at it tomorrow too.
Sebastian Wendel notifications@github.com schrieb:
Sent from my Android phone with K-9 Mail.
pbassut commentedon Sep 5, 2015
+1
pbassut commentedon Sep 5, 2015
So, I tried to find out what was happening in the code and looks like pydbgp.py couldn't initialise due a environment variable that it didn't recognised.
After running the following command(e.g. setting the required environment variables), it worked: