On Mi, 01 Nov 2023, varun bali wrote:
> We've identified a SIGSEGV crash in Vim at malloc() (__libc_calloc) that
> might be related to issues when writing to the .viminfo file during the exit
> process. It looks like Vim is failing to write to the .viminfo file, here "
> write_viminfo() " function is called,
> Can you please help us point out some CVE's that might address this issue of
> segmentation fault or memory corruption.
No I cannot. Please verify first with updated master version. If you can
still reproduce the issue, get a debugging build and get us a proper
stack trace of the crash and/or provide us with an ASAN log. But I
assume, current master doesn't have the problem.
Thanks,
Chris
--
I'm going to Boston to see my doctor. He's a very sick man.
-- Fred Allen
--
--
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].
To view this discussion on the web visit
https://groups.google.com/d/msgid/vim_dev/ZUJN2ZRHcZi36N59%40256bit.org.
