On 26 December 2013 13:43, Tony Mechelynck wrote: > Hm, you're removing the directory you're working on and replacing it by a > file of the same name, then asking to follow the hardlink ./.. in it, which > you implicitly just removed? Sounds to me like you were asking for trouble, > but well…
Of course I'm not saying this is something users do regularly, I just happened to do this and got this crash so since I was able to reproduce it I reported it. If there's a way to gracefully handle this situation then fine, otherwise too bad. > To compile Vim yourself (current version is 7.4.131 but your runtime files > seem a little out-of-date) see: I already compile Vim by myself, but I thought that runtime files were automatically pulled by Mercurial now that CVS is now longer used. Maybe that's a version of Netrw I installed myself and it somehow takes priority over the Mercurial's one, I'll check that. On 26 December 2013 13:50, Lech Lorens wrote: > Can you specify how you "Open foo"? I selected the file and pressed > return. Yep, that's what I do. On 26 December 2013 14:01, Dominique Pellé wrote: > If you can reproduce it, can you give a stack trace > with gdb, and also try to reproduce it with valgrind > or address sanitizer? I'm not sure how to get a meaningful stack trace: I compiled Vim with -g and ran it with GDB, but all I get in the log file is: Starting program: /usr/local/bin/vim Program received signal SIGSEGV, Segmentation fault. 0x00007ffff770e078 in main_arena () from /lib/x86_64-linux-gnu/libc.so.6 A debugging session is active. Inferior 1 [process 27106] will be killed. As for Valgrind I never used it, any explanation on how to get it running with Vim? -- -- You received this message from the "vim_dev" 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_dev" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/groups/opt_out.
