On Sat, Apr 14, 2012 at 1:56 PM, lilydjwg <[email protected]> wrote:
> On Sat, Apr 14, 2012 at 12:27:55PM -0500, Thomas Dziedzic wrote:
>> [...]
>>
>> It seems that str is for some reason getting set to null even if
>> everything appears to be ok..
>> Nick's comment also makes me think it might possibly have something to
>> do with the recent gcc 4.7 update.
>
> Hi, I just upgraded those packages and compiled if_python.o again, and
> I got the same crash. However, it won't crash if I add CFLAGS=-g then
> re-compile.
>
> --
> Best regards,
> lilydjwg
>
> Linux Vim Python 我的博客:
> http://lilydjwg.is-programmer.com/
> --
> A: Because it obfuscates the reading.
> Q: Why is top posting so bad?
>
> --
> 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
I couldn't reproduce this and it still crashes for me with
options=('!buildflags' '!makeflags').
If you could, can you see if you can get the vim PKGBUILD to build
without the segfault?
This will provide a point of reference so I can see what are the exact
changes that are needed to stop the segfault.
--
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
