Date: Sun, 02 Nov 2014 14:06:37 +0100 From: =?windows-1252?Q?Ren=E9_Ladan?= <rene@freebsd.org> To: freebsd-chromium@freebsd.org Subject: Re: Still segfault at start Message-ID: <54562C5D.5050603@freebsd.org> In-Reply-To: <20141102100531.GA5218@lena.kiev> References: <20141102100531.GA5218@lena.kiev>
next in thread | previous in thread | raw e-mail | index | archive | help
On 02-11-2014 11:05, Lena@lena.kiev.ua wrote:
> 8.4 i386, one more newer version 38.0.2125.111 from
> pkg.FreeBSD.org/freebsd:8:x86:32 - at start
> this time a window frame didn't appear, again segfault:
>
> (deleted ~/.config/chromium, ~/.cache/chromium, ~/.pki)
> ~ $ LD_LIBRARY_PATH=/usr/local/lib/gcc48 chrome --ssl-version-min=tls1
> Segmentation fault (core dumped)
> ~ $ gdb /usr/local/share/chromium/chrome chrome.core
> ...
> (gdb) bt
> #0 0x2dde2f37 in getframeaddr () from /usr/local/lib/libexecinfo.so.1
> #1 0x2dddeb21 in backtrace () from /usr/local/lib/libexecinfo.so.1
> #2 0x08729104 in std::vector<std::string, std::allocator<std::string> >::_M_range_insert<__gnu_cxx::__normal_iterator<std::string*, std::vector<std::string, std::allocator<std::string> > > > ()
> #3 0x089baef2 in std::_Rb_tree<std::string, std::pair<std::string const, std::string>, std::_Select1st<std::pair<std::string const, std::string> >, std::less<std::string>, std::allocator<std::pair<std::string const, std::string> > >::erase ()
> #4 0x088e558f in std::_Rb_tree<std::string, std::pair<std::string const, std::string>, std::_Select1st<std::pair<std::string const, std::string> >, std::less<std::string>, std::allocator<std::pair<std::string const, std::string> > >::_M_insert_unique_<std::pair<std::string const, std::string> const&> ()
> #5 0x088e4ba4 in std::_Rb_tree<std::string, std::pair<std::string const, std::string>, std::_Select1st<std::pair<std::string const, std::string> >, std::less<std::string>, std::allocator<std::pair<std::string const, std::string> > >::_M_insert_unique_<std::pair<std::string const, std::string> const&> ()
> #6 0x34fa7b30 in ?? ()
> #7 0xbfbfdd50 in ?? ()
> #8 0x00000000 in ?? ()
> (gdb)
I could reproduce this crash in an 8.4-i386 VM. Just wondering, what
happens if you rebuild chromium without GCC at all (replacing
USES=compiler:c++11-lib by a hardcoded
BUILD_DEPENDS=clang33:${PORTSDIR}/lang/clang33 ) ?
Regards,
René
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?54562C5D.5050603>