On Wednesday, May 11, 2016 at 12:17:03 PM UTC-7, Dominique Pelle wrote: > Frew Schmidt <[email protected]> wrote: > > > On Wednesday, May 11, 2016 at 2:18:31 AM UTC-7, Dominique Pelle wrote: > >> [ ... ] > >> Thanks. I should add: asan writes errors (if any) on stderr by default, > >> and since vim puts the terminal in cooked mode, asan error can be > >> garbled. So it's best to redirect stderr. The ASAN_OPTIONS > >> environment variable can be used for this. I put this in my ~/.bashrc: > >> > >> export > >> ASAN_OPTIONS="check_initialization_order=1:strict_init_order=1:detect_stack_use_after_return=1:detect_leaks=0:log_path=/home/pel/asan.log:abort_on_error=1" > >> > >> The relevant part to redirect errors is "log_path=/home/pel/asan.log" > >> (obviously you can put a different file name) > >> > >> See https://github.com/google/sanitizers/wiki/AddressSanitizerFlags > >> for more details. > >> > >> > 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. > >> > >> It may not be so easy with a gdb stack alone: the memory error may > >> have happened much earlier than where the crash is detected in gdb. > >> That's why asan helps: if freed memory is accessed for example, the > >> error will be reported immediately when accessed, and asan will give > >> more information: > >> - the stack where freed memory is accessed > >> - the stack where memory was previously freed > >> - the stack where memory was previously allocated > >> > >> Regards > >> Dominique > > > > Ok, sounds good. I've set the logging to $HOME/asan-$$.pid. Will report > > back when I have results. > > > Hi Frew > > I downloaded your dotfiles from github and used them. > I noticed dotfiles for awesome so I suspected that you used > awesome and so I used it too. Awesome window manager > also happened to be used in the other crash reported a > few days ago. Awesome causes more resizes than non > tiling window manager, which I think is the key to reproduce > the bug. > > I managed to reproduce a crash with a asan build of > vim-7.4.1829 using your dotfile. I'm not sure that my > crash is related to your crash, but it's crash anyway. > Asan reports: > [ ... ]
I'm impressed! That's some solid dedication! 👏👏 Hopefully someone more well versed in C / vim (like Bram :) can get it fixed -- -- 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 [email protected]. For more options, visit https://groups.google.com/d/optout.
