On So, 09 Jul 2017, Aron Griffis wrote: > > > On Sun, Jul 9, 2017 at 3:24 PM, Dominique Pellé <dominique.pe...@gmail.com> > wrote: > > Can you reproduce the crash with valgrind? It may give > useful information. Just run vim as: > > $ valgrind --num-callers=50 --track-origins=yes ./vim 2> vg.log > > and vg.log will contain useful info if you manage to reproduce the bug. > > > Running under valgrind seems to prevent the segfault from happening.
I get the attached log. Best, Christian -- Windows ist kein Virus - ein Virus tut etwas. -- -- 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 vim_dev+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
valgrind.log.gz
Description: application/gzip
