Date: Wed, 05 Nov 2014 11:47:31 +0000 From: "Tomek" <tomek@apostata.org> To: freebsd-chromium@freebsd.org Subject: Re: Still segfault at start Message-ID: <b7ce42bdf581c2d84148281a66e3cc19@webmail.olejniczak.info> In-Reply-To: <5458E00E.6010008@freebsd.org> References: <5458E00E.6010008@freebsd.org> <5458898A.3030306@freebsd.org> <54562C5D.5050603@freebsd.org> <20141102100531.GA5218@lena.kiev> <0242ddfdf4f8ab796793d3f186e60d39@webmail.olejniczak.info> <36593714051f36274387c822a86dc293@webmail.olejniczak.info>
next in thread | previous in thread | raw e-mail | index | archive | help
Hi,
4 listopada 2014 15:18 - "René Ladan" <rene@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',
],
--
Best Wishes
Tomek
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?b7ce42bdf581c2d84148281a66e3cc19>