Skip site navigation (1)Skip section navigation (2)
Date:      Mon, 14 Nov 2011 12:34:32 +0200
From:      Volodymyr Kostyrko <c.kworr@gmail.com>
To:        =?UTF-8?B?UmVuw6kgTGFkYW4=?= <rene@freebsd.org>
Cc:        freebsd-chromium@freebsd.org
Subject:   Re: current chromium throws Trace/BPT Trap
Message-ID:  <4EC0EEB8.4060706@gmail.com>
In-Reply-To: <CADL2u4jFacgxvsH9-bWT7YghmjGSVQHn-ifkAXDCsyPrF3VHjg@mail.gmail.com>
References:  <CA%2B%2B=3%2BZZuvGEjJpcAxveieU%2B0siEYOt1V=y6hAKJ2YQicp=FLQ@mail.gmail.com> <CANcjpOBtRd_o6Eh10BJ1GTUjSngMZ2DUwHszYcwzz_9T01vjvQ@mail.gmail.com> <CA%2B%2B=3%2BbgYFA-wSTsFbz2g8zxbCpY=kV-RSe0HQQZ2uCskxWAxg@mail.gmail.com> <CANcjpODDw6iTwk72e9r0G1pYVotAw%2BQ6rSj5D95stPm3QxmAzg@mail.gmail.com> <CA%2B%2B=3%2BY-JL5UWYenM4iPPpu548GnkkoZq_CHMFmJHMpJ_wRqhQ@mail.gmail.com> <CANcjpODo-9kGREbRJsJMWhmcfLCOKe86BoFS9YhLUzWyaXfFcA@mail.gmail.com> <CA%2B%2B=3%2BYNnPTG=H5oBHS7W_WYbpdpYahtox_XHBOheJuZ0dqxuw@mail.gmail.com> <CADL2u4jFacgxvsH9-bWT7YghmjGSVQHn-ifkAXDCsyPrF3VHjg@mail.gmail.com>

next in thread | previous in thread | raw e-mail | index | archive | help
10.11.2011 13:01, René Ladan wrote:
> 2011/11/10 Volodymyr Kostyrko<c.kworr@gmail.com>:
>> 2011/11/9 George Liaskos<geo.liaskos@gmail.com>:
>>> I am not sure if the problem is with the base or chrome... I've added
>>> René, he reported the issue with clang to me.
>>
>> This can be base. I have built chrome with gcc46 with same luck, just
>> now it says `bad address`. Sorry, I have compiled only non-debug
>> version, so there's all backtrace I can give:
>>
> [snip trace]
>
> I rebuilt all my ports this week on my laptop because of base/ports openssl
> conflicts and chose base gcc as the compiler for all ports unless some port
> insisted on another lang/gcc* version (including chromium). With just
> CODECS and GCONF, chromium 15.0.874.106 works fine (world and
> kernel are still built with clang, 9.0-rc2-amd64).
>
> I assume you use the default versions for your ports (ok, I have
> WITHOUT_NOUVEAU defined to make the binary NVidia driver work)
>
> Regards,
> René

I found the cause. google-perftools-1.8.3 works incorrectly when 
compiled with clang. After recompilation with stock gcc everything works 
fine.

-- 
Sphinx of black quartz judge my vow.



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