Skip site navigation (1)Skip section navigation (2)
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,=0A=0A4 listopada 2014 15:18 - "Ren=C3=A9 Ladan" <rene@freebsd.org>:: =
=0A=0A> Hm, maybe a 32 vs 64 bit issue. I'll try conditionally zeroing ou=
t the=0A> result value in libexecinfo as you described, but I only have 3=
2-bits=0A> VMs to test with (my physical CPU misses required VT-x) and al=
l hosts=0A> run 10.0.=0A=0AThe 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 a=
dded -fomit-frame-pointer at the and of CFLAGS.=0A=0APlease check if it w=
orks for You.=0A=0A--- third_party/ffmpeg/ffmpeg.gyp.orig	2014-11-05 13:3=
4:06.000000000 +0100=0A+++ third_party/ffmpeg/ffmpeg.gyp	2014-11-05 13:35=
:24.000000000 +0100=0A@@ -213,6 +213,12 @@=0A               'cflags!': [=
=0A                 '-fno-omit-frame-pointer',=0A               ],=0A+   =
           'cflags_c': [=0A+                '-fomit-frame-pointer',=0A+  =
            ],=0A+              'cflags_cc': [=0A+                '-fomit=
-frame-pointer',=0A+              ],=0A               'debug_extra_cflags=
!': [=0A                 '-fno-omit-frame-pointer',=0A               ], =
=0A=0A=0A--=0ABest Wishes=0ATomek



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?b7ce42bdf581c2d84148281a66e3cc19>