-
Notifications
You must be signed in to change notification settings - Fork 494
DLOG(INFO) not working anymore in 132 #3871
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Comments
Chromium has additional logging configuration that may help. See https://www.chromium.org/for-testers/enable-logging/ |
Oddly some INFO and WARNING logs do make it into debug.log, but at least I can get everything (INFO and WARNING) in stderr and stdout, based on the information in that link above. I still don't understand the inconsistency between the two now. |
Nothing changed in Note that no log calls will get into debug.log file before CEF was initialized, as log settings are passed only then. |
Thanks @cztomczak and @magreenblatt, the issue is likely related to the timing of CEF initialization as you note. I'll keep an eye out and share any additional insights if I find them. |
Closing for now. We can reopen if a bug is identified. |
Describe the bug
I have created a console application using CEF that was built for debug (NDEBUG is not defined).
The DLOG(INFO) << "Log Message" code no longer displays any message in console window. It was working in 124.
DLOG(ERROR) << "Log Message" still displays the message in console.
The CefSettings.log_severity is set to cef_log_severity_t::LOGSEVERITY_INFO which should allow DLOG(INFO) to display.
A debug.log file is created and it contains some information but not my info message. The messages from debug.log file are not displayed in console window.
Is there any option to restore the behavior from 124?
Versions (please complete the following information):
The text was updated successfully, but these errors were encountered: