FATAL check and stack trace not logged to debug.log file

Having problems with building or using CEF's C/C++ APIs? This forum is here to help. Please do not post bug reports or feature requests here.

FATAL check and stack trace not logged to debug.log file

Postby Czarek » Sun Nov 25, 2018 8:34 am

I am running cefclient application on Fedora 25. When using my own build (Release mode) and there is a FATAL check in Renderer process then I can see this FATAL check logged in debug.log file along with a full stack trace also written to that file. However when using binaries from Spotify (standard distribution) and there is a FATAL check failing I see no indication of it in logs (neither in console). Neither the FATAL check is logged and nor the stack trace when using Spotify binaries. Tried both Debug/Release versions with Spotify binaries and the result is the same. In my build I use the settings from the AutomatedBuildSetup wiki page with a few changes. I guess a GN arg that might affect the difference in behavior is "is_official_build=False". I can understand that the stack trace is not logged with Spotify binaries, because it is an official build. However it also does not even write the FATAL check to debug.log (even in Debug configuration binaries). Is this expected behavior?

Tested with "cef_binary_3.3538.1850.ge710be4_linux64".
Maintainer of the CEF Python, PHP Desktop and CEF C API projects. I'm available for contract work, see my resume.
User avatar
Posts: 1829
Joined: Sun Nov 06, 2011 2:12 am

Return to Support Forum

Who is online

Users browsing this forum: Google [Bot] and 11 guests