Re: debugging vim via gdb, best practices

Greg Mattson wrote:

> I was wondering, what is the best method to use for debugging vim itself?
>
> I'd like to be able to load up an interactive vim session in one
> window, and attach to the vim process in another, be able to set
> breakpoints, etc in such a way that I minimize the interference to the
> underlying process.
>
> is attaching to the vim pid workable? or is there a better more
> dedicated solution, one sort of like python's RemotePdb which allows
> you to telnet into the process itself?

You can use the terminal debugger. See ":help terminal-debug".
I made it especially to be able to debug Vim (also while travelling,
thus it doesn't depend on a GUI or IDE).

--
hundred-and-one symptoms of being an internet addict:
146. You experience ACTUAL physical withdrawal symptoms when away
from your 'puter and the net.

/// Bram Moolenaar -- Bram@Moolenaar.net -- http://www.Moolenaar.net \\\
/// sponsor Vim, vote for features -- http://www.Vim.org/sponsor/ \\\
\\\ an exciting new programming language -- http://www.Zimbu.org ///
\\\ help me help AIDS victims -- http://ICCF-Holland.org ///

--
--
You received this message from the "vim_use" maillist.
Do not top-post! Type your reply below the text you are replying to.
For more information, visit http://www.vim.org/maillist.php

---
You received this message because you are subscribed to the Google Groups "vim_use" group.
To unsubscribe from this group and stop receiving emails from it, send an email to vim_use+unsubscribe@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.