Clewn

Pardon my ignorance. Is this for using gdb to debug vim itself or a 
gdb-vim integration for use in better debugging of any piece of software?



Xavier de Gaye wrote:

>Hi all
>
>Clewn and vimGdb 1.6 have been released.
>
>The clewn project implements full gdb support in the vim editor:
>breakpoints, watch variables, gdb command completion, assembly
>windows, etc.
>
>You can get clewn and vimGdb from <http://clewn.sourceforge.net>.
>
>
>Here are the release notes:
>
>Clewn new features:
>
>VIM is forked by clewn when starting. A new command line option
>'-f', can be used to customize how gvim is run.
>
>The gdb program that is forked by clewn can have command line
>arguments, as for example in:
>clewn -p 'gdb --args foobar "this is foobar argument"'
>
>Support for cross compilation.
>
>The new command line option '-x' allows to do remote debugging of a
>target where Clewn and GDB are running, from a host where the
>development is done and where VIM is running.
>
>Clewn changes:
>
>Option '-r' has its meaning reverted, now clewn sets the SO_REUSEADDR
>socket option by default.
>Option '-v' (disable variables watching) has been removed.
>Option '-i' (disable saving history in .clewn_history) has been removed.
>Option '-m' (enable GDB prompt for more messages) has been removed.
>
>
>Clewn bug fix:
>
>The following bug has been fixed: when a watched variable is deleted,
>the watched variables feature is not functionnal anymore.
>
>
>VimGdb new feature:
>
>The gdb program that is forked by Vim can have command line
>arguments. For example, you can set the Vim gdbprg variable to:
>
>    :set gdbprg=gdb\ --args\ foobar\ \"this\ is\ foobar\ argument\"
>
>
>Xavier
>
>--
>http://clewn.sourceforge.net           gdb support in Vim
>
>
>  
>

Russell Bateman wrote:

> Pardon my ignorance. Is this for using gdb to debug vim itself or a 
> gdb-vim integration for use in better debugging of any piece of software?

AFAIK, it is for the second meaning, why not visit the 
http://clewn.sourceforge.net to get more details?
Good Luck!

BR
Linsong

>
>
>
> Xavier de Gaye wrote:
>
>> Hi all
>>
>> Clewn and vimGdb 1.6 have been released.
>>
>> The clewn project implements full gdb support in the vim editor:
>> breakpoints, watch variables, gdb command completion, assembly
>> windows, etc.
>>
>> You can get clewn and vimGdb from <http://clewn.sourceforge.net>.
>>
>>
>> Here are the release notes:
>>
>> Clewn new features:
>>
>> VIM is forked by clewn when starting. A new command line option
>> '-f', can be used to customize how gvim is run.
>>
>> The gdb program that is forked by clewn can have command line
>> arguments, as for example in:
>> clewn -p 'gdb --args foobar "this is foobar argument"'
>>
>> Support for cross compilation.
>>
>> The new command line option '-x' allows to do remote debugging of a
>> target where Clewn and GDB are running, from a host where the
>> development is done and where VIM is running.
>>
>> Clewn changes:
>>
>> Option '-r' has its meaning reverted, now clewn sets the SO_REUSEADDR
>> socket option by default.
>> Option '-v' (disable variables watching) has been removed.
>> Option '-i' (disable saving history in .clewn_history) has been removed.
>> Option '-m' (enable GDB prompt for more messages) has been removed.
>>
>>
>> Clewn bug fix:
>>
>> The following bug has been fixed: when a watched variable is deleted,
>> the watched variables feature is not functionnal anymore.
>>
>>
>> VimGdb new feature:
>>
>> The gdb program that is forked by Vim can have command line
>> arguments. For example, you can set the Vim gdbprg variable to:
>>
>>    :set gdbprg=gdb\ --args\ foobar\ \"this\ is\ foobar\ argument\"
>>
>>
>> Xavier
>>
>> -- 
>> http://clewn.sourceforge.net           gdb support in Vim
>>
>>
>>  
>>
>

> Clewn and vimGdb 1.6 have been released.

Do you have any plans to support native gdb on win32 i.e. MinGW?

Sergey Khorev wrote:
>> Clewn and vimGdb 1.6 have been released.

> Do you have any plans to support native gdb on win32 i.e. MinGW?

VimGdb runs on Cygwin. I don't know MinGW, but it seems you can use
MinGW from Cygwin as stated in:

    http://www.mingw.org/mingwfaq.shtml#faq-usingwithcygwin

So you should be able to run the gdb of MinGW from Vim in Cygwin after
Vim has been patched with vimGdb (note that Vim on Cygwin is the
console version only).

On the other hand, I think it could be difficult to support gdb from
clewn or vimGdb in a MinGW environnment. Clewn and vimGdb rely on unix
system calls.  And another problem with clewn is that it uses the
NetBeans protocol to talk to Vim, and Vim currently supports NetBeans
only when running with GTK or Motif.

Xavier

--
http://clewn.sourceforge.net           gdb support in Vim

> So you should be able to run the gdb of MinGW from Vim in Cygwin after
> Vim has been patched with vimGdb

Sounds too complicated to be very useful :))

> And another problem with clewn is that it uses the
> NetBeans protocol to talk to Vim, and Vim currently supports NetBeans
> only when running with GTK or Motif.

Actually Vim supports Netbeans on Win32 in the same degree as on Gtk or Mot=
if.

Sergey Khorev wrote:
>> So you should be able to run the gdb of MinGW from Vim in Cygwin after
>> Vim has been patched with vimGdb
> 
> Sounds too complicated to be very useful :))
> 
>> And another problem with clewn is that it uses the
>> NetBeans protocol to talk to Vim, and Vim currently supports NetBeans
>> only when running with GTK or Motif.
> 
> Actually Vim supports Netbeans on Win32 in the same degree as on Gtk or Motif.

gvim for native-Windows GUI (which can be compiled under Cygwin even
though it doesn't need Cygwin to run) does (but of course it doesn't
understand Cygwin-like paths such as /cygdrive/c/). IIUC, gvim for
Cygwin X11 doesn't, unless compiled with GTK or Motif. AFAIK, no version
of Console Vim supports Netbeans.


Best regards,
Tony.

A. J. Mechelynck wrote:
> Sergey Khorev wrote:
>> ...
>>> And another problem with clewn is that it uses the
>>> NetBeans protocol to talk to Vim, and Vim currently supports NetBeans
>>> only when running with GTK or Motif.
>>
>> Actually Vim supports Netbeans on Win32 in the same degree as on Gtk or 
>> Motif.
>
> gvim for native-Windows GUI (which can be compiled under Cygwin even
> though it doesn't need Cygwin to run) does (but of course it doesn't
> understand Cygwin-like paths such as /cygdrive/c/). IIUC, gvim for
> Cygwin X11 doesn't, unless compiled with GTK or Motif. AFAIK, no version
> of Console Vim supports Netbeans.

This few weeks old thread (flamewar actually):

http://sources.redhat.com/ml/gdb-patches/2006-02/msg00052.html

brings some light (to a Windows-illiterate like me) on why one wants
to use minGw when there is already this great master work named
Cygwin.  It looks like the gdb maintainers want to support minGw. So a
port of clewn to minGw is a good idea.

I don't think I am quite up to it though and help would be very much
welcome. Sergey, you did the port of netBeans and cscope in Vim to
win32, what do you think ?

Xavier


--
http://clewn.sourceforge.net           gdb support in Vim

> http://sources.redhat.com/ml/gdb-patches/2006-02/msg00052.html
>
> brings some light (to a Windows-illiterate like me) on why one wants
> to use minGw when there is already this great master work named
> Cygwin.  It looks like the gdb maintainers want to support minGw. So a
> port of clewn to minGw is a good idea.

Additionally I can admit why I don't use Cygwin: it's overkill for
most my tasks (I use make, gcc, gdb and a couple of UnxUtils from
http://unxutils.sf.net)

BTW there is a native version of gdb (without cygwin1.dll) on MinGW
site for several years. And it works with Agide on Win32 so it is
possible to implement gdb + Netbeans link on Windows :)

> I don't think I am quite up to it though and help would be very much
> welcome. Sergey, you did the port of netBeans and cscope in Vim to
> win32, what do you think ?

Well, I had a quick look at clewn sources.
There are no `obstack', `poll' or terminal control stuff on Windows.
`fork' -> `spawn' like in Vim's if_cscop.c
`select' can be used on sockets only
There are special OS primitives for waiting on terminal input instead
of `select' (WaitForSingleObject, WaitForMultipleObjects).

So it seems it's possible but might require significant effort. I'd
take part in this but now I have to many TODO items in other
open-source projects. Probably I will if someone else don't outdo me.

--
Sergey Khorev
http://iamphet.nm.ru
Can anybody think of a good tagline I can steal?

Sergey Khorev wrote:
>> I don't think I am quite up to it though and help would be very much
>> welcome. Sergey, you did the port of netBeans and cscope in Vim to
>> win32, what do you think ?
>
> Well, I had a quick look at clewn sources.
> There are no `obstack', `poll' or terminal control stuff on Windows.
> `fork' -> `spawn' like in Vim's if_cscop.c
> `select' can be used on sockets only
> There are special OS primitives for waiting on terminal input instead
> of `select' (WaitForSingleObject, WaitForMultipleObjects).
>
> So it seems it's possible but might require significant effort. I'd
> take part in this but now I have to many TODO items in other
> open-source projects. Probably I will if someone else don't outdo me.

Thanks for the tips. Having a look at gdb might help too, they do use
obstack and some sort of terminal control.

And thanks for your help offer.

Xavier

--
http://clewn.sourceforge.net           gdb support in Vim

Mark Smithfield wrote:
> Is it possible to use Clewn with OSX?
>
> I see that Clewn requires NetBeans, and I am not sure
> whether vim can be compiled with NetBeans support on
> OSX. The makefile says no, but there are other
> indications that NetBeans works on osx. I would LOVE
> to have Clewn on the mac, but this is a little beyond
> my grasp, where to start, don't you know.

NetBeans is a protocol and is certainly implemented on OSX by some IDE
applications.

The NetBeans implementation in Vim requires GTK or Motif. I don't know
OSX, so I cannot help much here. Try to install GTK or Motif on OSX
(using XDarwin and Fink ?).

Also, you may try to get help from the Vim mailing lists: vim@...
and vim-dev@.... The Vim community is always very helpful. You
must suscribe first at http://www.vim.org.

Xavier

--
http://clewn.sourceforge.net           gdb support in Vim

Xavier de Gaye wrote:

> The netbeans command 'setDot' does not look for a window having
> already the requested buffer displayed and instead, always replaces
> the buffer in the current window with the requested buffer (the result
> may be that two windows are displaying the same buffer). It would be
> nice to have the same behavior as the ":drop" command.
> 
> Here is a proposed fix (context diff to Vim 6.4):

Makes sense.  I think this can also be used in the other places where
the Netbeans interface uses set_curbuf().

-- 
hundred-and-one symptoms of being an internet addict:
269. You receive an e-mail from the wife of a deceased president, offering
     to send you twenty million dollar, and you are not even surprised.

 /// Bram Moolenaar -- Bram@... -- http://www.Moolenaar.net   \\\
///        sponsor Vim, vote for features -- http://www.Vim.org/sponsor/ \\\
\\\        download, build and distribute -- http://www.A-A-P.org        ///
 \\\            help me help AIDS victims -- http://www.ICCF.nl         ///