Date: Mon, 03 Nov 2014 18:39:13 +0000 From: "Tomek" <tomek@apostata.org> To: chromium@freebsd.org Subject: Re: Still segfault at start Message-ID: <0242ddfdf4f8ab796793d3f186e60d39@webmail.olejniczak.info> In-Reply-To: <54562C5D.5050603@freebsd.org> References: <54562C5D.5050603@freebsd.org> <20141102100531.GA5218@lena.kiev>
index | next in thread | previous in thread | raw e-mail
Hi, 2 listopada 2014 14:06 - "René Ladan" <rene@freebsd.org>:: > 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 The problem lies in backtrace from execinfo - in stack_trace_posix.cc line 751: count_ = base::saturated_cast<size_t>(backtrace(trace_, arraysize(trace_))); The solution is either comment it out and return 0 or add -fno-omit-frame-pointer in CFLAGS in port Makefile. I've tested it on FreeBSD 8.4 in VirtualBox. Can anybody test it also? This is not really a chromium problem - it is broken execinfo... -- Best Wishes Tomekhelp
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?0242ddfdf4f8ab796793d3f186e60d39>