Adding the Mac Vim mailing list. On Thu, Jan 19, 2012 at 8:27 AM, Phil Dobbin <phildob...@gmail.com> wrote: > On 19/1/12 15:59, "Charles Campbell" <charles.e.campb...@nasa.gov> wrote: >> Phil Dobbin wrote: >>> Hi, all. >>> >>> For the first time since I seriously started using Vim about six months ago >>> I got this message on startup: >>> >>> `Vim: Caught deadly signal ABRT Vim: Finished. Abort trap` >>> >>> I'd been using it all day& had just come back to it. This version of Vim >>> (7.3 Included patches: 1-244, 246-353) is on OS X& I compiled it myself >>> back in December& has worked fine. I subsequently got it back working by >>> removing the FuzzyFinder plugin which I had recollections of reading about >>> being troublesome some while ago but had since been fixed so whether this >>> was a lucky guess or not I'm not sure. As an aside MacVim on the same >>> machine worked fine when the terminal one wasn't working. >>> >>> Seeing as this is first problem I've had in this respect, can anyone advise >>> on the best way to troubleshoot this kind of occurrence? I've Googled on it >>> but nothing much came up. I've also got a copy of the crash log if that's >>> any help to anybody. >>> >> * try to get a reproducible example; preferably with vim -u NONE . >> Barring that, try to isolate to a minimal .vimrc and minimal qty of plugins. >> * I'm not familiar with OS-X; under linux, I'd advise compiling with -g >> and getting a core dump. Find out where the crash occurred (file, line >> number), and values of pertinent variables >> * see if valgrind helps > > Hi, Chip. > > Thanks for the reply. > > The relevant part of the crash log as far as I can see is: > > `Exception Type: EXC_CRASH (SIGABRT) > Exception Codes: 0x0000000000000000, 0x0000000000000000 > Crashed Thread: 0 Dispatch queue: com.apple.main-thread > > Application Specific Information: > abort() called > > Thread 0 Crashed: Dispatch queue: com.apple.main-thread > 0 libSystem.B.dylib 0x00007fff891000b6 __kill + 10 > 1 vim 0x00000001000df604 0x100000000 + > 914948 > 2 libSystem.B.dylib 0x00007fff891121ba _sigtramp + 26 > 3 libSystem.B.dylib 0x00007fff891000b6 __kill + 10 > 4 libSystem.B.dylib 0x00007fff891a09f6 abort + 83 > 5 libSystem.B.dylib 0x00007fff890b8195 free + 128 > 6 dyld 0x00007fff5fc06d5f` > > Going on what I could glean from that & what I read at: > > <http://www.gnu.org/s/libc/manual/html_node/Program-Error-Signals.html> > > is that Vim aborted before it crashed on launch. Starting Vim -u NONE it > functioned as normal & upon removing a couple of plugins it reverted to > normal. > > Modifying `libSystem.B.dylib 0x00007fff891000b6 __kill + 10` to make it a > viable search term in Google/Stack Overflow turns up scores of entries of > crashes across several different applications on OS X Snow Leopard (which is > the OS this particular version of Vim of mine crashed on) so it may seem > reasonable to conjecture that this problem is OS specific. The odd thing > however, is that the gui version MacVim functioned normally the whole time > with the same plugins & vimrc. > > Cheers, > > Phil...
-- /George V. Reilly geo...@reilly.org Twitter: @georgevreilly http://www.georgevreilly.com/blog http://blogs.cozi.com/tech -- 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
