debugging vim via gdb, best practices

all,

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?

thanks much for any info here.. this is as much for my education as it is to track down any particular bug..

--
--
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.