-
Notifications
You must be signed in to change notification settings - Fork 289
Ensure that warn! output is visible in client outputs. #1677
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
I don't think it's necessarily a responsibility of WR. |
There's an existing bug (from @nical I think) about providing an interface for C++ clients to access a logging stream (perhaps via callback). This is probably related to that. |
In gecko we have various ways to log warnings. The one that I am interested in having some plumbing for in webrender is the gfxCriticalError/gfxCriticalNote that saves the log in the crash reports. We tend to use it sparingly, only in places where we are likely to crash soon and the logged information would helps with investigating the issue. It is super useful. |
@nical sounds good. Could you create a Bugzilla item for this? |
There we go: https://bugzilla.mozilla.org/show_bug.cgi?id=1399389 |
I have some updates for this in https://bugzilla.mozilla.org/show_bug.cgi?id=1399389. |
The associated bugzilla bugs are fixed. |
No description provided.
The text was updated successfully, but these errors were encountered: