[email protected] wrote: > Vim is hardlocking for me on every single run on my FreeBSD 5.4 > system. I've tried 7.2.299, 7.2.309 and 7.2.315 and all are broken. > > It appears to compile fine, but on run, it fails to respond to any > keystrokes and eats nearly 100% of my CPU till I send it a > SIGKILL...Please help. :) > > Thanks
You can attach to the running process with gdb and look at the stack trace with 'backtrace' gdb command. You can also use the 'continue' gdb command and interrupt again with CTRL-C to run 'backtrace' several times (in case the backtrace is not always the same). Example: $ gdb ... (gdb) attach PID ... (gdb) backtrace ... (gdb) continue (gdb) CTRL-C (gdb) backtrace (replace PID with the process ID of the Vim process which hogs the CPU) The output of backtrace may help to figure out why it hogs the CPU. You will need to compile/link Vim with symbols (-g -O0) to get a proper stack trace with gdb. -- Dominique -- You received this message from the "vim_dev" maillist. For more information, visit http://www.vim.org/maillist.php
