Log to stderr/stdout AND debug.log file possible? (CEF 125+)

[natonicfp]

I'm updating my application to use chrome bootstrap + alloy style. I noticed after making the necessary changes that I stopped getting LOG/DLOG output to stderr/stdout, but still saw output in debug.log. Previously most log messages seemed to be present in both stdout/stderr and the debug.log. After digging a bit, it appeared it might be related to to chrome bootstrap (speculation after looking at this commit: https://github.com/chromiumembedded/cef ... /4e3668f93), so following instructions here (https://www.chromium.org/for-testers/enable-logging/), I passed enable-logging=stderr and log-level=0 and logging started appearing in stdout/stderr again, but the debug.log file is no longer populated.

Does the move to chrome bootstrap mean LOG/DLOG output is now an either/or proposition, or is there a way to get it to go to both from within the app (obviously, redirecting/tee of stdout/stderr is an option, but one I'd rather avoid if possible).

[ndesktop]

I think it's one or the other. I saw this too recently (around branch 127, but it might be sooner).

[Czarek]

Also noticed this issue on my Mac with CEF 130. It would be nice if things were logged to both terminal and log file as it worked before.

Looks like in Debug configuration it works fine, only in Release configuration it logs only to log file.