On Sat, Sep 2, 2023 at 5:02 AM Yegappan Lakshmanan <yegapp...@gmail.com> wrote: > > Hi all, > > The access control to readonly, read-write and private members in a > class/object discussed in https://github.com/vim/vim/discussions/12979 > should all work now. Let us know if there are any cases where the > access control is not correctly enforced. > > When testing these, I found an existing memory corruption issue > with class member variables. When a class member uses a complex > type (e.g. List or Dict), then it is garbage collected under some > conditions leading to a memory corruption (reported by ASAN and > Valgrind). I am still debugging this issue. >
Correction: This is a use-after-free problem and not a memory corruption. - Yegappan -- -- 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. To view this discussion on the web visit https://groups.google.com/d/msgid/vim_dev/CAAW7x7%3Dzemkp07%2BwqU3rPr6tMk9PTmQgp_tKa4Kc4RiJ1CbutA%40mail.gmail.com.
