Re: SIGBUS in Vim 7.4

On Tuesday, May 10, 2016 at 11:03:45 PM UTC-7, Dominique Pelle wrote:
> Frew Schmidt wrote:
>
> > Ok, so I built and installed a fresh vim according to
> > Dominique's instructions and attempted both asan and valgrind.
> > Either those things don't work together, or I can repro the bug
> > immediately. Here's the error:
>
> I should have said: valgrind and asan don't work together indeed.
> Either use a asan build, or use valgrind on a normal build (not stripped).
>
> Actually trying both tools (but not a the same time!) can be
> useful as some bugs are only found by one tool:
> - asan cannot find accesses to uninitialized memory
> - valgrind cannot find overflow to global and stack variables
>
> > Note that this issue is *very* rare, maybe happens every few weeks,
>
> It's likely to be easier to reproduce i.e less rare with asan or valgrind,
> as any access to freed memory will be detected for example, whereas
> without such tools, vim may often work by luck and once in a while
> crash.
>
> Regards
> Dominique

Ok, well I'll be running with the asan version till it happens again. If it doesn't happen in about a month I'll switch to the valgrind version.

FWIW though, I suspect that a skilled practitioner might be able to suss out the actual cause of the bug with the coredump I already have.

--
--
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

---
You received this message because you are subscribed to the Google Groups "vim_use" group.
To unsubscribe from this group and stop receiving emails from it, send an email to vim_use+unsubscribe@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.