Thiago Padilha <tpadilha84@gmail.com> wrote:
> Sometimes when I reattach to the tmux session after the virtual machine
> has been frozen for a long time vim freezes right away without consuming 100% cpu,
...
> This is really annoying me, I was hoping someone could give me hints on how to debug this issue.
You could build vim with debug information (-g -O0). Then, when bug
happens & Vim uses 100% of the CPU, you can attach with gdb to the
Vim process that hogs the CPU, and look at the stack trace. That may
give useful information to debug it.
$ gdb
(gdb) attach pid
(gdb) bt
(where pid is he process ID of the Vim process using 100% of the CPU)
You can then continue with...
(gdb) c
... and press CTRL-C in gdb to stop vim and run bt again to see if you
get similar stack trace. You can repeat that a few times to get a feeling
of what Vim is doing.
Dominique
--
--
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/groups/opt_out.
Friday, April 19, 2013
Subscribe to:
Post Comments (Atom)
No comments:
Post a Comment