chromium 34.0.1847.116 gives SIGABRT at start

[René Ladan]

Hi,

I updated the port to 34.0.1847.132 which starts but with rendering
errors (tabs and plugins crashing). It also dumps core but because I
made a Release build it contains no further information.

The svn patch for the Ports tree:
http://people.freebsd.org/~rene/patches/chromium-33-34.diff
SHA256 (chromium-33-34.diff) =
3a1a1859cb776ece867f133c92c441da48aef60df6fa67c2769d311fd35b86b2
SIZE = 212616

René

On 04/23/2014 15:54, René Ladan wrote:
> 2014-04-22 21:30 GMT+02:00 Robert Nagy <robert at openbsd.org
> <mailto:robert at openbsd.org>>:
> 
>     Hey,
> 
>     Try this:
> 
>     build/common.gypi:
> 
>     @@ -1322,7 +1322,7 @@
>                # TODO(jungshik): Turn this on on Android.
>                # For ChromeOS, this should be turned on in
>     chromeos-chrome.ebuild
>                # file as well by adding icu_use_data_file_flag=1 to
>     BUILD_DEFINES.
>     -          ['OS!="android"', {
>     +          ['OS!="android" and os_bsd!=1', {
>                  'icu_use_data_file_flag%': 1,
>                }],
>              ],
> 
> I tried the patch but unfortunately it doesn't help. I do get a core
> dump with a Release build so I'll see if that gives a clue.
> 
> René
> 
>     On (2014-04-22 21:21), René Ladan wrote:
>     > Hi,
>     >
>     > I ported chromium 34.0.1847.116 to FreeBSD (patches at [1]) but it
>     > currently gives a SIGABRT when starting it without any visible output.
>     >
>     > Building a debug version does not make a difference either.
>     >
>     > This is on FreeBSD 10.0-STABLE, GENERIC amd64 kernel.
>     >
>     > Does anyone see something obviously wrong with the patches that could
>     > result in a SIGABRT ?
>     >
>     > [1]
>     https://github.com/gliaskos/freebsd-chromium/tree/master/www/chromium
>     >