On Jan 15, 2008 8:26 PM, Gautam Iyer <[EMAIL PROTECTED]> wrote: > > Then "vim -u /tmp/vimrc -X" hangs when run under screen. It does not > display anything, or respond to terminal input (including Ctrl-C). When > killed (SIGTERM), it draws the intro screen and prints a message saying > "Received TERM signal, exiting."
I can't reproduce that. A couple of questions/suggestions: When it "hangs", does it take 100% of the CPU (endless loop) or is the vim process blocked (0% of CPU). You can check the CPU usage with the "top" command. You can also try to run vim with strace (useful in case it blocks in a system call?): $ strace vim 2> trace.log ... then look at trace.log You can also try to attach with gdb to the running process. You will first need to build vim with DEBUG information (-g -O0). Just put the following line in vim7/src/Makefile: CFLAGS = -g -O0 Then recompile vim and run it. When vim hangs, attach to the process with gdb as follows: $ gdb /usr/local/bin/vim process_id (replace /usr/local/bin/vim with actual location of your vim program and replace process_id with the process ID of vim). Then in gdb, type "bt" command to get a stack trace. It should help to debug. -- Dominique --~--~---------~--~----~------------~-------~--~----~ You received this message from the "vim_dev" maillist. For more information, visit http://www.vim.org/maillist.php -~----------~----~----~----~------~----~------~--~---
