On Wed, May 9, 2012 at 4:29 AM, Christian Brabandt <cbli...@256bit.org> wrote: > Hi Thomas! > > On Mi, 09 Mai 2012, Thomas Dziedzic wrote: > >> On Wed, Apr 25, 2012 at 10:56 PM, Thomas Dziedzic <gos...@gmail.com> wrote: >> >> It looks like this was caused by >> >> http://gcc.gnu.org/bugzilla/show_bug.cgi?id=53084. >> >> >> > >> > I will try to see if this was the problem once the next gcc snapshot >> > comes out (this weekend or next week) and try to report back here. >> >> Just tried out the latest gcc snapshot 4.7-20120505 >> This segfault still exists so it wasn't caused by gcc bug #53084. >> Also, here is a fedora bug report for the same thing: >> https://bugzilla.redhat.com/show_bug.cgi?id=817196 > > Shouldn't patch 497 avoid the crash? >
yes, but as the commit message suggests: "Avoid the crash, doesn't really fix the problem." http://code.google.com/p/vim/source/detail?r=e34c620007be9fd805556c43fe848de521f3b64c > regards, > Christian > > -- > 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 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
