I'm going to close the lldb session and start anew and track things with instruments.app maybe that will help. Too bad valgrind doesn't run on Mac OS X 10.9. Anyone here have suggestions for how to track memory for vim on a Mac?
On Thursday, December 19, 2013 12:07:15 AM UTC-8, Bjorn Tipling wrote: > On Wednesday, December 18, 2013 8:20:45 PM UTC-8, mattn wrote: > > Way to reproduce? > > It's difficult to reproduce, but the way I see these errors is to use the > timers patch from [1] while collaborating with others and our floobits > plugin. Basically calling set_timeout's that edit buffer contents. You can > probably reproduce it without the patch using autocmd on CursorHold, but it > may be more difficult. Three of us spent a great deal of time going through > vim's screen.c, windows.c and regexp.c trying to figure out how w_match_head > was getting stomped. I think we may run some software to detect it when > memory is being stomped/written over inappropriately. The problem is only > related to the timers/async code in that it can lead to things happening in > orders other than what vim traditionally assumes. The patch doesn't really > touch these files anywhere. > > Anyway, I have the lldb/gdb still open so if you have any additional > information you need I can provide it. I understand that maybe that given the > context of the patch not much action will happen, but maybe there's interest. > > > > [1] > https://groups.google.com/forum/#!topic/vim_dev/-4pqDJfHCsM%5B1-25-false%5D -- -- 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.
