Vdebug crash with small screen resolutions about vdebug HOT 24 CLOSED

Hi, it looks like there are two issues here.

The first is that where an error message should be you have some dodgy missing graphics - I don't know if that's a known issue with Macvim, but I've seen it every so often with Gvim too. The second thing looks like it's related to tabs. Do you know if your macvim has tab support built in? If not, Vdebug won't function correctly.

Try just running:

:tabnew

If you don't get a new tab then it's that. If not then let me know,

Cheers

from vdebug.

Hey Jonathan,

I am using the latest version of Macvim and there don't seem to be any issues created in the issue queue relating to this problem that I could find. I am able to create new tabs.

It seems to happen when I debug something and it ends and then I close all the windows and then try to debug again.

I just got this error message:

An error occured: <type 'exceptions.AttributeError'>
Traceback (most recent call last):
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 140, in run
self.ui.statuswin.set_status("running")
AttributeError: 'NoneType' object has no attribute 'set_status'

On Tuesday, 26 February 2013 at 2:37 AM, Jonathan Cairns wrote:

Hi, it looks like there are two issues here.
The first is that where an error message should be you have some dodgy missing graphics - I don't know if that's a known issue with Macvim, but I've seen it every so often with Gvim too. The second thing looks like it's related to tabs. Do you know if your macvim has tab support built in? If not, Vdebug won't function correctly.
Try just running:
:tabnew

If you don't get a new tab then it's that. If not then let me know,
Cheers

—
Reply to this email directly or view it on GitHub (#50 (comment)).

from vdebug.

Interesting, it looks like the windows aren't loading up correctly. It's possible that you don't have enough vertical space to create all the necessary split windows. Are you using a fairly small display, e.g. < 15''?

Could you show me the output of this command, running it after being focussed on a full height window in your Vim:

:echo winheight(0)

Hope that makes sense!

from vdebug.

Hey I am using vim on a macbook pro 2011 13 inch. When I ran that command it said 35. Also I noticed when I debug even though I have changed the keys it still says the default keys to start and stop the debugger.

On Tuesday, 26 February 2013 at 8:04 PM, Jonathan Cairns wrote:

Interesting, it looks like the windows aren't loading up correctly. It's possible that you don't have enough vertical space to create all the necessary split windows. Are you using a fairly small display, e.g. < 15''?
Could you show me the output of this command, running it after being focussed on a full height window in your Vim:
:echo winheight(0)

Hope that makes sense!

—
Reply to this email directly or view it on GitHub (#50 (comment)).

from vdebug.

Ok, thanks, it looks like the screen size is the problem. Obviously not your problem, but a problem with Vdebug :-)

Someone else raised an issue about being able to toggle windows, and I think that would solve this. However it's a pretty big overhaul, and unfortunately I'm not sure there's any short term fix that I can recommend. Having said that, it's definitely on the cards, so I'll keep you updated on any progress.

As for the key mapping, it sounds strange that changing the default mapping doesn't seem to work. I'll play around and see if I have the same problem.

Thanks

from vdebug.

Hey,

I am able to change the default key binds but in vdebug there a certain part where it said to start debugging even though I had changed it to wtf

On Tuesday, 26 February 2013 at 8:12 PM, Jonathan Cairns wrote:

Ok, thanks, it looks like the screen size is the problem. Obviously not your problem, but a problem with Vdebug :-)
Someone else raised an issue about being able to toggle windows, and I think that would solve this. However it's a pretty big overhaul, and unfortunately I'm not sure there's any short term fix that I can recommend. Having said that, it's definitely on the cards, so I'll keep you updated on any progress.
As for the key mapping, it sounds strange that changing the default mapping doesn't seem to work. I'll play around and see if I have the same problem.
Thanks

—
Reply to this email directly or view it on GitHub (#50 (comment)).

from vdebug.

Hey Jonathan,

I am getting this other problem that seems to be related to vdebug as well. For some reason it is stopping me from visually selecting anything in my php file. If I try to visually select something it crashes with the following error message:

An error occured: <type 'exceptions.AttributeError'>
Traceback (most recent call last):
File "/Users/gdance/.vim/bundle/vdebug/plugin/python/start_vdebug.py", line 103, in handle_visual_eval
return self.event_dispatcher.visual_eval()
File "/Users/gdance/.vim/bundle/vdebug/plugin/python/vdebug/event.py", line 13, in visual_eval
return event.execute(self.runner)
File "/Users/gdance/.vim/bundle/vdebug/plugin/python/vdebug/event.py", line 61, in execute
runner.eval(selection)
File "/Users/gdance/.vim/bundle/vdebug/plugin/python/vdebug/runner.py", line 207, in eval
context_res = self.api.eval(code)
AttributeError: 'NoneType' object has no attribute 'eval'

Right before this I tried to remove a breakpoint that I had left in my php file. I was not able to remove the breakpoint either ;) If you need me to send you anymore information then just ask.

Take care,
Gary

On Tuesday, 26 February 2013 at 8:46 PM, Gary Dance wrote:

Hey,

I am able to change the default key binds but in vdebug there a certain part where it said to start debugging even though I had changed it to wtf

On Tuesday, 26 February 2013 at 8:12 PM, Jonathan Cairns wrote:

Ok, thanks, it looks like the screen size is the problem. Obviously not your problem, but a problem with Vdebug :-)
Someone else raised an issue about being able to toggle windows, and I think that would solve this. However it's a pretty big overhaul, and unfortunately I'm not sure there's any short term fix that I can recommend. Having said that, it's definitely on the cards, so I'll keep you updated on any progress.
As for the key mapping, it sounds strange that changing the default mapping doesn't seem to work. I'll play around and see if I have the same problem.
Thanks

—
Reply to this email directly or view it on GitHub (#50 (comment)).

from vdebug.

Hi @gdance,

The two things that you raised in the previous two messages are two separate bugs, so I've created new issues for them, #52 and #51.

Thanks

from vdebug.

Oh ok I thought they might of been related.
On Mar 1, 2013 12:44 AM, "Jonathan Cairns" [email protected] wrote:

Hi @gdance https://github.com/gdance,

The two things that you raised in the previous two messages are two
separate bugs, so I've created new issues for them, #52https://github.com/joonty/vdebug/issues/52and
#51 #51.

Thanks

—
Reply to this email directly or view it on GitHubhttps://github.com//issues/50#issuecomment-14233675
.

from vdebug.

No worries! Thanks for helping to improve Vdebug - you found lots of issues :)

This issue will remain open and related to the fact that small screen resolutions don't work with Vdebug yet.

from vdebug.

Hmm well it works it just seems to run into issues if I debug something
then stop it then try to debug something again. That is when all these
errors seem to happen.the first time I debug everything works fine.
On Mar 1, 2013 8:03 PM, "Jonathan Cairns" [email protected] wrote:

No worries! Thanks for helping to improve Vdebug - you found lots of
issues :)

This issue will remain open and related to the fact that small screen
resolutions don't work with Vdebug yet.

—
Reply to this email directly or view it on GitHubhttps://github.com//issues/50#issuecomment-14278731
.

from vdebug.

Ok, thanks for the extra information.

from vdebug.

No probs if I think of anything else I'll email and I'd you need me to send
any more stuff then just ask
On Mar 1, 2013 8:07 PM, "Jonathan Cairns" [email protected] wrote:

Ok, thanks for the extra information.

—
Reply to this email directly or view it on GitHubhttps://github.com//issues/50#issuecomment-14278829
.

from vdebug.

Actually, I'm having trouble working out what the error is, because of the missing text on your Vim. Could you create a log file before running Vdebug with:

:VdebugOpt debug_file /path/to/file.log
:VdebugOpt debug_file_level 2

Then start vdebug, keep going until you get the error and then paste the output here? Or in a gist if it's too long.

Thanks

from vdebug.

Hey here is the first debugging attempt. This time I didn’t set any breakpoints and just stepped over and into a few things. I noticed when the debugging session ended I wasn't able to stop it and clear all the debugging windows away when I hit . They just stayed there and eventually it said unable to connect and then finally cleared all the windows away.

On Friday, 1 March 2013 at 8:40 PM, Jonathan Cairns wrote:

Actually, I'm having trouble working out what the error is, because of the missing text on your Vim. Could you create a log file before running Vdebug with:
:VdebugOpt debug_file /path/to/file.log :VdebugOpt debug_file_level 2

Then start vdebug, keep going until you get the error and then paste the output here? Or in a gist if it's too long.
Thanks

—
Reply to this email directly or view it on GitHub (#50 (comment)).

from vdebug.

oh and also I forgot to mention I tried to debug before that and got that weird graphical glitch again but then it said that the debug log file didn't exist so I had to close vim and try again

On Friday, 1 March 2013 at 8:40 PM, Jonathan Cairns wrote:

Actually, I'm having trouble working out what the error is, because of the missing text on your Vim. Could you create a log file before running Vdebug with:
:VdebugOpt debug_file /path/to/file.log :VdebugOpt debug_file_level 2

Then start vdebug, keep going until you get the error and then paste the output here? Or in a gist if it's too long.
Thanks

—
Reply to this email directly or view it on GitHub (#50 (comment)).

from vdebug.

Hi I tried again and this time it didn't log anything and just gave me the problem in the 2nd screenshot and wouldn't let me close the drubbing windows when I hit Also in the other screenshot it still has the default key bindings listed to start and stop debugging even though I have changed them to something else. They should probably be updated to reflect what I have changed them to since there isn't much point in showing them if they don't work lol

On Friday, 1 March 2013 at 11:02 PM, Gary Dance wrote:

oh and also I forgot to mention I tried to debug before that and got that weird graphical glitch again but then it said that the debug log file didn't exist so I had to close vim and try again

On Friday, 1 March 2013 at 8:40 PM, Jonathan Cairns wrote:

Actually, I'm having trouble working out what the error is, because of the missing text on your Vim. Could you create a log file before running Vdebug with:
:VdebugOpt debug_file /path/to/file.log :VdebugOpt debug_file_level 2

Then start vdebug, keep going until you get the error and then paste the output here? Or in a gist if it's too long.
Thanks

—
Reply to this email directly or view it on GitHub (#50 (comment)).

from vdebug.

I tried again and set two breakpoints and it crashed I think because it couldn't find the log file. It might be good for debug to make sure the log file exists when I set it with :VdebugOpt debug file ~/vdebug.log instead of crashing when it tries to write to it after I start debugging. I have attached the screenshot as well in case that isn't what the problem was lol here is what the error message left in :messages was.

Traceback (most recent call last):
File "", line 1, in
File "/Users/gdance/.vim/bundle/vdebug/plugin/python/start_vdebug.py", line 33, in run
self.handle_exception(e)
File "/Users/gdance/.vim/bundle/vdebug/plugin/python/start_vdebug.py", line 234, in handle_exception
self.handle_readable_error(e)
File "/Users/gdance/.vim/bundle/vdebug/plugin/python/start_vdebug.py", line 205, in handle_readable_error
self.runner.ui.error(str(e))
File "/Users/gdance/.vim/bundle/vdebug/plugin/python/vdebug/ui/vimui.py", line 138, in error
vdebug.log.Log(string,vdebug.log.Logger.ERROR)
File "/Users/gdance/.vim/bundle/vdebug/plugin/python/vdebug/log.py", line 100, in init
Log.log(string,level)
File "/Users/gdance/.vim/bundle/vdebug/plugin/python/vdebug/log.py", line 105, in log
l.log(string,level)
File "/Users/gdance/.vim/bundle/vdebug/plugin/python/vdebug/log.py", line 90, in log
self.__open()
File "/Users/gdance/.vim/bundle/vdebug/plugin/python/vdebug/log.py", line 76, in __open
%(self.filename,str(e)))
vdebug.log.LogError: Invalid file name '/vdebug.log' for log file: [Errno 2] No such file or directory: '/vdebug.log'

On Friday, 1 March 2013 at 11:02 PM, Gary Dance wrote:

oh and also I forgot to mention I tried to debug before that and got that weird graphical glitch again but then it said that the debug log file didn't exist so I had to close vim and try again

On Friday, 1 March 2013 at 8:40 PM, Jonathan Cairns wrote:

Actually, I'm having trouble working out what the error is, because of the missing text on your Vim. Could you create a log file before running Vdebug with:
:VdebugOpt debug_file /path/to/file.log :VdebugOpt debug_file_level 2

Then start vdebug, keep going until you get the error and then paste the output here? Or in a gist if it's too long.
Thanks

—
Reply to this email directly or view it on GitHub (#50 (comment)).

from vdebug.

Hey Johnathan,

I just tried again and that time everything worked fine. The only thing I noticed is that after I stopped debugging and cleared the windows away and did a :ls is that these weird buffers had been created I noticed that there seem to be a lot of strange buffers that get created after I finish debugging. I have attached a screenshot of the ones that were created this time.

On Friday, 1 March 2013 at 11:26 PM, Gary Dance wrote:

I tried again and set two breakpoints and it crashed I think because it couldn't find the log file. It might be good for debug to make sure the log file exists when I set it with :VdebugOpt debug file ~/vdebug.log instead of crashing when it tries to write to it after I start debugging. I have attached the screenshot as well in case that isn't what the problem was lol here is what the error message left in :messages was.

Traceback (most recent call last):
File "", line 1, in
File "/Users/gdance/.vim/bundle/vdebug/plugin/python/start_vdebug.py", line 33, in run
self.handle_exception(e)
File "/Users/gdance/.vim/bundle/vdebug/plugin/python/start_vdebug.py", line 234, in handle_exception
self.handle_readable_error(e)
File "/Users/gdance/.vim/bundle/vdebug/plugin/python/start_vdebug.py", line 205, in handle_readable_error
self.runner.ui.error(str(e))
File "/Users/gdance/.vim/bundle/vdebug/plugin/python/vdebug/ui/vimui.py", line 138, in error
vdebug.log.Log(string,vdebug.log.Logger.ERROR)
File "/Users/gdance/.vim/bundle/vdebug/plugin/python/vdebug/log.py", line 100, in init
Log.log(string,level)
File "/Users/gdance/.vim/bundle/vdebug/plugin/python/vdebug/log.py", line 105, in log
l.log(string,level)
File "/Users/gdance/.vim/bundle/vdebug/plugin/python/vdebug/log.py", line 90, in log
self.__open()
File "/Users/gdance/.vim/bundle/vdebug/plugin/python/vdebug/log.py", line 76, in __open
%(self.filename,str(e)))
vdebug.log.LogError: Invalid file name '/vdebug.log' for log file: [Errno 2] No such file or directory: '/vdebug.log'

On Friday, 1 March 2013 at 11:02 PM, Gary Dance wrote:

oh and also I forgot to mention I tried to debug before that and got that weird graphical glitch again but then it said that the debug log file didn't exist so I had to close vim and try again

On Friday, 1 March 2013 at 8:40 PM, Jonathan Cairns wrote:

Actually, I'm having trouble working out what the error is, because of the missing text on your Vim. Could you create a log file before running Vdebug with:
:VdebugOpt debug_file /path/to/file.log :VdebugOpt debug_file_level 2

Then start vdebug, keep going until you get the error and then paste the output here? Or in a gist if it's too long.
Thanks

—
Reply to this email directly or view it on GitHub (#50 (comment)).

Attachments:

• Screenshot at Mar 01 23-21-59.png

from vdebug.

Oh and also I am not sure if this might have something to do with it but my mappings for vdebug are the following:

" Vdebug mapping
let g:vdebug_keymap = {
\ "run" : "wtf",
\ "run_to_cursor" : "rtc",
\ "step_over" : "",
\ "step_into" : "",
\ "step_out" : "",
\ "close" : "",
\ "detach" : "",
\ "set_breakpoint" : "br",
\ "get_context" : "env",
\ "eval_under_cursor" : "euc",
}

On Friday, 1 March 2013 at 11:36 PM, Gary Dance wrote:

Hey Johnathan,

I just tried again and that time everything worked fine. The only thing I noticed is that after I stopped debugging and cleared the windows away and did a :ls is that these weird buffers had been created I noticed that there seem to be a lot of strange buffers that get created after I finish debugging. I have attached a screenshot of the ones that were created this time.

On Friday, 1 March 2013 at 11:26 PM, Gary Dance wrote:

I tried again and set two breakpoints and it crashed I think because it couldn't find the log file. It might be good for debug to make sure the log file exists when I set it with :VdebugOpt debug file ~/vdebug.log instead of crashing when it tries to write to it after I start debugging. I have attached the screenshot as well in case that isn't what the problem was lol here is what the error message left in :messages was.

Traceback (most recent call last):
File "", line 1, in
File "/Users/gdance/.vim/bundle/vdebug/plugin/python/start_vdebug.py", line 33, in run
self.handle_exception(e)
File "/Users/gdance/.vim/bundle/vdebug/plugin/python/start_vdebug.py", line 234, in handle_exception
self.handle_readable_error(e)
File "/Users/gdance/.vim/bundle/vdebug/plugin/python/start_vdebug.py", line 205, in handle_readable_error
self.runner.ui.error(str(e))
File "/Users/gdance/.vim/bundle/vdebug/plugin/python/vdebug/ui/vimui.py", line 138, in error
vdebug.log.Log(string,vdebug.log.Logger.ERROR)
File "/Users/gdance/.vim/bundle/vdebug/plugin/python/vdebug/log.py", line 100, in init
Log.log(string,level)
File "/Users/gdance/.vim/bundle/vdebug/plugin/python/vdebug/log.py", line 105, in log
l.log(string,level)
File "/Users/gdance/.vim/bundle/vdebug/plugin/python/vdebug/log.py", line 90, in log
self.__open()
File "/Users/gdance/.vim/bundle/vdebug/plugin/python/vdebug/log.py", line 76, in __open
%(self.filename,str(e)))
vdebug.log.LogError: Invalid file name '/vdebug.log' for log file: [Errno 2] No such file or directory: '/vdebug.log'

On Friday, 1 March 2013 at 11:02 PM, Gary Dance wrote:

oh and also I forgot to mention I tried to debug before that and got that weird graphical glitch again but then it said that the debug log file didn't exist so I had to close vim and try again

On Friday, 1 March 2013 at 8:40 PM, Jonathan Cairns wrote:

Actually, I'm having trouble working out what the error is, because of the missing text on your Vim. Could you create a log file before running Vdebug with:
:VdebugOpt debug_file /path/to/file.log :VdebugOpt debug_file_level 2

Then start vdebug, keep going until you get the error and then paste the output here? Or in a gist if it's too long.
Thanks

—
Reply to this email directly or view it on GitHub (#50 (comment)).

Attachments:

• Screenshot at Mar 01 23-21-59.png

Attachments:

• Screenshot at Mar 01 23-32-30.png

from vdebug.

Oh and I forgot here is the last vdebug.log from the last time.

On Friday, 1 March 2013 at 11:38 PM, Gary Dance wrote:

Oh and also I am not sure if this might have something to do with it but my mappings for vdebug are the following:

" Vdebug mapping
let g:vdebug_keymap = {
\ "run" : "wtf",
\ "run_to_cursor" : "rtc",
\ "step_over" : "",
\ "step_into" : "",
\ "step_out" : "",
\ "close" : "",
\ "detach" : "",
\ "set_breakpoint" : "br",
\ "get_context" : "env",
\ "eval_under_cursor" : "euc",
}

On Friday, 1 March 2013 at 11:36 PM, Gary Dance wrote:

Hey Johnathan,

I just tried again and that time everything worked fine. The only thing I noticed is that after I stopped debugging and cleared the windows away and did a :ls is that these weird buffers had been created I noticed that there seem to be a lot of strange buffers that get created after I finish debugging. I have attached a screenshot of the ones that were created this time.

On Friday, 1 March 2013 at 11:26 PM, Gary Dance wrote:

I tried again and set two breakpoints and it crashed I think because it couldn't find the log file. It might be good for debug to make sure the log file exists when I set it with :VdebugOpt debug file ~/vdebug.log instead of crashing when it tries to write to it after I start debugging. I have attached the screenshot as well in case that isn't what the problem was lol here is what the error message left in :messages was.

Traceback (most recent call last):
File "", line 1, in
File "/Users/gdance/.vim/bundle/vdebug/plugin/python/start_vdebug.py", line 33, in run
self.handle_exception(e)
File "/Users/gdance/.vim/bundle/vdebug/plugin/python/start_vdebug.py", line 234, in handle_exception
self.handle_readable_error(e)
File "/Users/gdance/.vim/bundle/vdebug/plugin/python/start_vdebug.py", line 205, in handle_readable_error
self.runner.ui.error(str(e))
File "/Users/gdance/.vim/bundle/vdebug/plugin/python/vdebug/ui/vimui.py", line 138, in error
vdebug.log.Log(string,vdebug.log.Logger.ERROR)
File "/Users/gdance/.vim/bundle/vdebug/plugin/python/vdebug/log.py", line 100, in init
Log.log(string,level)
File "/Users/gdance/.vim/bundle/vdebug/plugin/python/vdebug/log.py", line 105, in log
l.log(string,level)
File "/Users/gdance/.vim/bundle/vdebug/plugin/python/vdebug/log.py", line 90, in log
self.__open()
File "/Users/gdance/.vim/bundle/vdebug/plugin/python/vdebug/log.py", line 76, in __open
%(self.filename,str(e)))
vdebug.log.LogError: Invalid file name '/vdebug.log' for log file: [Errno 2] No such file or directory: '/vdebug.log'

On Friday, 1 March 2013 at 11:02 PM, Gary Dance wrote:

oh and also I forgot to mention I tried to debug before that and got that weird graphical glitch again but then it said that the debug log file didn't exist so I had to close vim and try again

On Friday, 1 March 2013 at 8:40 PM, Jonathan Cairns wrote:

Actually, I'm having trouble working out what the error is, because of the missing text on your Vim. Could you create a log file before running Vdebug with:
:VdebugOpt debug_file /path/to/file.log :VdebugOpt debug_file_level 2

Then start vdebug, keep going until you get the error and then paste the output here? Or in a gist if it's too long.
Thanks

—
Reply to this email directly or view it on GitHub (#50 (comment)).

Attachments:

• Screenshot at Mar 01 23-21-59.png

Attachments:

• Screenshot at Mar 01 23-32-30.png

from vdebug.

Hey Johnathan,

I just debugged again and I noticed that when I stepped over a variable that had a really big string in it like $homecam_description the watch window displays with all these @ symbols.

The homecam_description variable contains this:

Lorem ipsum dolor sit amet, consectetuer adipiscing elit. Aenean commodo ligula eget dolor. Aenean massa. Cum sociis natoque penatibus et magnis dis parturient montes, nascetur ridiculus mus. Donec quam felis, ultricies nec, pellentesque eu, pretium quis, sem. Nulla consequat massa quis enim. Donec pede justo, fringilla vel, aliquet nec, vulputate eget, arcu. In enim justo, rhoncus ut, imperdiet a, venenatis vitae, justo. Nullam dictum felis eu pede mollis pretium. Integer tincidunt. Cras dapibus. Vivamus elementum semper nisi. Aenean vulputate eleifend tellus. Aenean leo ligula, porttitor eu, consequat vitae, eleifend ac, enim. Aliquam lorem ante, dapibus in, viverra quis, feugiat a, tellus. Phasellus viverra nulla ut metus varius laoreet. Quisque rutrum. Aenean imperdiet. Etiam ultricies nisi vel augue. Curabitur ullamcorper ultricies nisi. Nam eget dui. Etiam rhoncus. Maecenas tempus, tellus eget condimentum rhoncus, sem quam semper libero, sit amet adipiscing sem neque sed ipsum. Nam quam nunc, blandit vel, luctus pulvinar, hendrerit id, lorem. Maecenas nec odio et ante tincidunt tempus. Donec vitae sapien ut libero venenatis faucibus. Nullam quis ante. Etiam sit amet orci eget eros faucibus tincidunt. Duis leo. Sed fringilla mauris sit amet nibh. Donec sodales sagittis magna. Sed consequat, leo eget bibendum sodales, augue velit cursus nunc,

I have attached a screenshot of this problem as well. For some reason I haven't been able to reproduce the other crashing issues though :( I will keep trying though.

Hopefully all these emails aren't too big lol. Anyway here is the screenshot of the watch window when I step over the $homecam_description variable. You can see that it is just filled with all the @ symbols instead of showing the variables.

On Friday, 1 March 2013 at 11:38 PM, Gary Dance wrote:

Oh and also I am not sure if this might have something to do with it but my mappings for vdebug are the following:

" Vdebug mapping
let g:vdebug_keymap = {
\ "run" : "wtf",
\ "run_to_cursor" : "rtc",
\ "step_over" : "",
\ "step_into" : "",
\ "step_out" : "",
\ "close" : "",
\ "detach" : "",
\ "set_breakpoint" : "br",
\ "get_context" : "env",
\ "eval_under_cursor" : "euc",
}

On Friday, 1 March 2013 at 11:36 PM, Gary Dance wrote:

Hey Johnathan,

I just tried again and that time everything worked fine. The only thing I noticed is that after I stopped debugging and cleared the windows away and did a :ls is that these weird buffers had been created I noticed that there seem to be a lot of strange buffers that get created after I finish debugging. I have attached a screenshot of the ones that were created this time.

On Friday, 1 March 2013 at 11:26 PM, Gary Dance wrote:

I tried again and set two breakpoints and it crashed I think because it couldn't find the log file. It might be good for debug to make sure the log file exists when I set it with :VdebugOpt debug file ~/vdebug.log instead of crashing when it tries to write to it after I start debugging. I have attached the screenshot as well in case that isn't what the problem was lol here is what the error message left in :messages was.

Traceback (most recent call last):
File "", line 1, in
File "/Users/gdance/.vim/bundle/vdebug/plugin/python/start_vdebug.py", line 33, in run
self.handle_exception(e)
File "/Users/gdance/.vim/bundle/vdebug/plugin/python/start_vdebug.py", line 234, in handle_exception
self.handle_readable_error(e)
File "/Users/gdance/.vim/bundle/vdebug/plugin/python/start_vdebug.py", line 205, in handle_readable_error
self.runner.ui.error(str(e))
File "/Users/gdance/.vim/bundle/vdebug/plugin/python/vdebug/ui/vimui.py", line 138, in error
vdebug.log.Log(string,vdebug.log.Logger.ERROR)
File "/Users/gdance/.vim/bundle/vdebug/plugin/python/vdebug/log.py", line 100, in init
Log.log(string,level)
File "/Users/gdance/.vim/bundle/vdebug/plugin/python/vdebug/log.py", line 105, in log
l.log(string,level)
File "/Users/gdance/.vim/bundle/vdebug/plugin/python/vdebug/log.py", line 90, in log
self.__open()
File "/Users/gdance/.vim/bundle/vdebug/plugin/python/vdebug/log.py", line 76, in __open
%(self.filename,str(e)))
vdebug.log.LogError: Invalid file name '/vdebug.log' for log file: [Errno 2] No such file or directory: '/vdebug.log'

On Friday, 1 March 2013 at 11:02 PM, Gary Dance wrote:

oh and also I forgot to mention I tried to debug before that and got that weird graphical glitch again but then it said that the debug log file didn't exist so I had to close vim and try again

On Friday, 1 March 2013 at 8:40 PM, Jonathan Cairns wrote:

Actually, I'm having trouble working out what the error is, because of the missing text on your Vim. Could you create a log file before running Vdebug with:
:VdebugOpt debug_file /path/to/file.log :VdebugOpt debug_file_level 2

Then start vdebug, keep going until you get the error and then paste the output here? Or in a gist if it's too long.
Thanks

—
Reply to this email directly or view it on GitHub (#50 (comment)).

Attachments:

• Screenshot at Mar 01 23-21-59.png

Attachments:

• Screenshot at Mar 01 23-32-30.png

from vdebug.

Hi,

Just a couple of things first off:

1. I'm afraid that none of your attachments came through to Github. It's normally best to upload things like log files as a Gist, and images are attachable on the Github web interface.
2. The last 5 messages were an information overload! There have been many different issues discussed in this thread, which should really relate to a single issue. If you think you've discovered a new one then please open a new Github issue - it's easier for me to maintain that way :)

Right, on to the issues, working backwards.

• The @ symbol thing is something that Vim does to very long strings, when it can't show the entire line of a string. If you scroll down then the whole string should become visible
• The log file is created if it doesn't exist. The reason an error is occurring for you is that you've used the '~' shortcut to mean the home directory. Vdebug doesn't currently support that for the log files, but it's been raised as an issue, see #53. For the time being use the full, expanded file path
• The strange buffer list issue might be related, but then again it might not - given a bit more information we can work out whether it's a new issue or not

Could you create a log file and upload it as a Gist, after having a session where the original error occurs?

Thanks

from vdebug.

it will be massively hard to debug on small screen resultions so closing this

from vdebug.