On 06/05/09 09:01 +0800, Dasn wrote: > Hi guys, I wrote a toy which builds communications between VIM and > debuggers. The tool's main function is tracing the instruction pointer > in VIM while we debugging the program. That should be similar to Emacs's > Gud, I suppose. :) > > Here it is: > http://lrc.sf.net/bride-0.1.1.tar.gz > > And some screen shots: > http://lrc.sf.net/shot1.jpg > http://lrc.sf.net/shot2.jpg > > "make && make install" will do all the jobs for you. > For more info, see ":h Bride" in VIM. > > As the development just begins, it currently only supports two > debuggers: 'gdb' and 'pdb' (python's debugger), and was only tested on > OpenBSD. > > Any comments are appreciated. > > I'm not on misc@, please Cc me, thanks. >
The current cvs version can be fetched via: $ cvs -z3 -d:pserver:[email protected]:/cvsroot/lrc \ checkout -P Bride I've added the OpenBSD license and fixed some bugs. This project is just in exploratory stage, I'm still not sure if it's the right way to go. The main problem is: As VIM has no support for built-in terminals, it's hard to guess WHEN the debugger should give its prompt and WHAT kind of prompt it will provide. For example, the program may read from stdin, in which case the debugger has no output; and the user program may also provide its own prompt, say a readline program. Currently I set a timeout value for the client when it talking to the debugger, if no response returns, the client will give up and report a timeout error. That is an ugly solution really... -- Dasn
