Still segfault at start
René Ladan
rene at freebsd.org
Mon Nov 3 19:51:09 UTC 2014
On 03-11-2014 19:39, Tomek wrote:
> Hi,
>
> 2 listopada 2014 14:06 - "René Ladan" <rene at freebsd.org>::
>> On 02-11-2014 11:05, Lena at 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?
Thanks for the information. I'll try adding the flag (there does not
seem to be a bundled execinfo). it might fix Chromium on 9.X too.
> This is not really a chromium problem - it is broken execinfo...
So Chromium is one of the few ports that is affected by it...
Regards,
René
More information about the freebsd-chromium
mailing list