Still segfault at start

[René Ladan]

On 05-11-2014 12:47, Tomek wrote:
> Hi,
>
> 4 listopada 2014 15:18 - "René Ladan" <rene at freebsd.org>:: 
>
>> Hm, maybe a 32 vs 64 bit issue. I'll try conditionally zeroing out the
>> result value in libexecinfo as you described, but I only have 32-bits
>> VMs to test with (my physical CPU misses required VT-x) and all hosts
>> run 10.0.
> The problem is that ffmpeg needs -fomit-frame-pointer in 32 bit. The below patch should fix it - for unknown reason gyp cflags_c! or cflags_cc! doesn't remove -fno-omit-frame-pointer so I've added -fomit-frame-pointer at the and of CFLAGS.
>
> Please check if it works for You.
>
> --- third_party/ffmpeg/ffmpeg.gyp.orig	2014-11-05 13:34:06.000000000 +0100
> +++ third_party/ffmpeg/ffmpeg.gyp	2014-11-05 13:35:24.000000000 +0100
> @@ -213,6 +213,12 @@
>                'cflags!': [
>                  '-fno-omit-frame-pointer',
>                ],
> +              'cflags_c': [
> +                '-fomit-frame-pointer',
> +              ],
> +              'cflags_cc': [
> +                '-fomit-frame-pointer',
> +              ],
>                'debug_extra_cflags!': [
>                  '-fno-omit-frame-pointer',
>                ], 
>
Chrome indeed starts with this in my 8.4-i386 VM. This fixes
ports/193610 right?

René