z99 / vimpdb

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

Failed to start debugging #1

Open GoogleCodeExporter opened 9 years ago

GoogleCodeExporter commented 9 years ago
1) Documentation accessible via :help is missing
2) VimPdb.vim definitely must be in unix line endings format (:set ff=unix)
3) When started in GUI (gvim), pressed the F5, got the message "Xlib:
unexpected async reply (sequence 0x9cb)!". It seems like a threading
problem, all X11 events must be processed within the main thread.

Original issue reported on code.google.com by sakh...@gmail.com on 17 Oct 2007 at 8:07

GoogleCodeExporter commented 9 years ago
[deleted comment]
GoogleCodeExporter commented 9 years ago
1) + 2) Will be taken care of
3) In which line was the exception raised? The new thread uses the Python "vim"
module to execute commands (that do highlighting, for example). That probably 
leads
to the X11 commands for the GVim redrawing. I'll fix it (but it requires a bit 
more
time). Anyway, on Windows it didn't cause any trouble, so I didn't notice it.

Original comment by budow...@gmail.com on 18 Oct 2007 at 12:34

GoogleCodeExporter commented 9 years ago
Right, you can't send call any Xlib function from a different thread. When I
developed a GUI application, I had to do all paintings in the context of the 
main
thread, where the Xlib session had been initialized. And when I needed to redraw
something, I had to use thread synchronization primitives instead of X11 
messages.
This is exactly our situation. Once there was a warning of threading issues of 
the
vim python module somewhere in the vim mailing lists.

Original comment by sakh...@gmail.com on 18 Oct 2007 at 12:58

GoogleCodeExporter commented 9 years ago
You could overcome these problems by using vim's servermode.

I don't know, though, if that works for Windows. At last on X11 driven
UNIX machines that should work better (and is more sane IMHO). On macs
you need to use the all-new shiny MacVim.

I tried to use VimPdb with MacVim, but it seems to leak memory, as
I get warnings during run-time on the console.

I'll try to implement a version of the PdbIDE class which uses the server
mode of vim.

Original comment by stefan.e...@gmail.com on 19 Nov 2007 at 11:56

GoogleCodeExporter commented 9 years ago
@stefan.eletzhofer:
Have you reached a usable point with PdbIDE and the vim server mode?

Original comment by phxx...@gmail.com on 7 Oct 2008 at 9:21

GoogleCodeExporter commented 9 years ago
I noticed (2) is still not taken care of.

Original comment by brianh...@gmail.com on 17 May 2011 at 2:17

GoogleCodeExporter commented 9 years ago
[deleted comment]
GoogleCodeExporter commented 9 years ago
Point 2) I encountered on a Ubuntu system but was able to fix
Point 3) unfortunately met as well, but unsolved so far --> run into fatal 
errors after pressing F5

Original comment by slagter....@gmail.com on 4 Dec 2011 at 12:47