search

z99 / vimpdb

Automatically exported from code.google.com/p/vimpdb
0 stars 0 forks source link

Gvim exits when a second breakpoint is set in vimpdb with "fatal IO error" #4

Open GoogleCodeExporter opened 9 years ago

GoogleCodeExporter commented 9 years ago 
What steps will reproduce the problem?

1. Install vimpdb, and start gvim on a python file with a couple of
assignements
2. Press F5 to start debugging
3. Set a break point on a line (foo = 2 for example) with F2
4. Set a break point on another line (bar = 3 for example) with F2

What is the expected output? What do you see instead?

The second line should be highlighted in red as the first, to indicate the
presence of a breakpoint.
Instead, Gvim exits within half a second (approximately) with this error
printed on the console:
gvim: Fatal IO error 11 (Resource temporarily unavailable) on X server :0.0.

What version of the product are you using? On what operating system?

I use the latest vimpdb, with Gvim 7.2.79, on Ubuntu 9.04

Please provide any additional information below.

Original issue reported on code.google.com by eric.kedji on 24 May 2009 at 11:05

GoogleCodeExporter commented 9 years ago 
For me, just pressing F5 on even "Hello World" gives the same error. Same 
platform.

Original comment by YuviPa...@gmail.com on 26 May 2009 at 11:13

GoogleCodeExporter commented 9 years ago 
Any news on this? Pretty useless plugin at this point.

Original comment by stevv...@gmail.com on 4 Dec 2009 at 10:49

GoogleCodeExporter commented 9 years ago 
GVim exits with an error, vim from terminal runs nicely. Version  7.2, Ubuntu 
9.10.

Original comment by kirzha...@gmail.com on 5 Dec 2009 at 8:47