On Fri, Jan 30, 2015 at 07:59:19PM -0500, Jakson Alves de Aquino wrote: > On Sat, Jan 31, 2015 at 12:14:14AM +0100, Dominique Pellé wrote: > > In the stack, I see update_screen() being called twice as > > a result of a screen resize event. Maybe that's causing the > > problem. > > You might be right. I was running Vim inside Tmux (Ubuntu 14.10) > and it splits the Tmux window to start R. So, the size of the > screen changes while the Vim function StartR() is being executed. > If I run either Vim not in Tmux or GVim, R is started in another > terminal emulator and there is no crash. > > > I don't know how to reproduce it. > > > > Can you try to reproduce it after recompiling Vim with the > > address sanitizer (asan)? It's only a matter of compiling > > and linking with -fsanitize=address. It assumes that your > > compiler is recent enough (gcc >= 4.8 or clang >= 3.3?) > > With the patch, it crashes and seems to output the same backtrace > of gdb, but I cannot see the first lines, even if I try to scroll > the Tmux pane.
Sorry, I applied the patch wrongly because there was a line break in the longest line. After applying it correctly, the output that I can copy in Tmux copy mode is: 0x0c2c80017c20: fa fa fa fa fa fa fa fa fa fa fa fa fa fa fa fa 0x0c2c80017c30: fd fd fd fd fd fd fd fd fd fd fd fd fd fd fd fd 0x0c2c80017c40: fd fd fd fd fd fd fd fd fd fd fd fd fd fd fd fd 0x0c2c80017c50: fd fd fd fd fd fd fd fd fd fd fd fd fd fd fd fd 0x0c2c80017c60: fd fd fd fd fd fd fd fd fd fd fd fd fd fd fd fd Shadow byte legend (one shadow byte represents 8 application bytes): Addressable: 00 Partially addressable: 01 02 03 04 05 06 07 Heap left redzone: fa Heap right redzone: fb Freed heap region: fd Stack left redzone: f1 Stack mid redzone: f2 Stack right redzone: f3 Stack partial redzone: f4 Stack after return: f5 Stack use after scope: f8 Global redzone: f9 Global init order: f6 Poisoned by user: f7 Contiguous container OOB:fc ASan internal: fe ==4435==ABORTING > > Please also try to run vim with valgrind (without building with asan) > > It may find other bugs than asan: uninitialized memory accesses > > are not found by asan but they are found by valgrind. > > Running vim with valgrind, before the patch, there is no crash. -- -- 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/d/optout.
