On 4/19/2012 3:59 PM, Thomas Dziedzic wrote:
Ok, I'm getting closer to figuring this out, it's caused by having the -O2 flag there. If you remove -O2 from CFLAGS, there is no crash. I'm guessing this has something to do with gcc 4.7.0 possibly
While it may be an optimizer bug, and things like
#2 0x00000000005a9912 in OutputWrite (self=<optimized out>, args=<optimized out>) at if_py_both.h:82
make one suspicious. It might be that there is some "lucky" code. -ernie -- 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
