Comment #11 on issue 267 by [email protected]: Segmentation
fault with if_lua (during or after the GC)
https://code.google.com/p/vim/issues/detail?id=267
I think I jumped to quickly at Lua. From the BT I think the problem lies
either > within vim's own garbage collector or in the set_ref_in_item()
[1] function.
I found a discussion which sounds familiar at [2]. However, I tried out
the vimscript snippet and it does not cause a segfault. In the meantime,
I'm still getting regularly segfaults using the neocomplete plugin.
Any hints on how to build vim with debugging symbols?
[1] http://fossies.org/dox/vim-7.4/eval_8c_source.html#l06944
[2] https://groups.google.com/d/msg/vim_dev/Nr8Ja4Zjghw/3FfMjVobHmoJ
If it is actually the same crash, I made a patch, but it is not complete
yet for LUA because I did not know how to get a return value from LUA code
in the case of a failed garbage collect.
To get the snippet in that thread to cause a crash, you may need to
increase the number of iterations used in the script.
Here is the discussion on the patch:
https://groups.google.com/d/topic/vim_dev/dnN58kO5Vg4/discussion
Here is the discussion of remaining work:
https://groups.google.com/forum/#!topic/vim_dev/RzHGXmVewvc
--
You received this message because this project is configured to send all
issue notifications to this address.
You may adjust your notification preferences at:
https://code.google.com/hosting/settings
--
--
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.
