From 20c29df3114b66696a6118858d8fa4e98c2f7de9 Mon Sep 17 00:00:00 2001 From: sairathnavamsi Date: Sun, 5 Apr 2015 01:43:13 -0700 Subject: [PATCH] Updated Log Filters (markdown) --- Log-Filters.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/Log-Filters.md b/Log-Filters.md index 5e9fb91..213a205 100644 --- a/Log-Filters.md +++ b/Log-Filters.md @@ -1,4 +1,4 @@ -Citra supports configurable filtering of log message per-class. This is especially useful if you're debugging a subsystem and want very detailed messages from it or if you want to silence some annoyingly spammy errors (e.g. unimplemented GPU features.) +Citra supports configurable filtering of log message per-class. This is especially useful if you're debugging a subsystem and want very detailed messages from it or if you want to silence some annoyingly spamming errors (e.g. unimplemented GPU features.) Messages are filtered in each class according to their severity, the filter will block all messages in the class that are below the configured severity. The severity levels are: - `Trace`: Extremely detailed and repetitive (many times per frame) debugging information that is likely to pollute logs. @@ -10,7 +10,7 @@ Messages are filtered in each class according to their severity, the filter will Note that `Trace` is *permanently filtered out in non-Debug builds* for performance reasons. -Class names can be discovered from the log messages themselves. For example, this message is in the class `Service`: +Class names can be discovered from the log messages themselves. For example, this message is in the class `Service`: ``` [ 10.285042] Service core/hle/service/service.h:Service::Interface::SyncRequest:84: unknown/unimplemented function '0x01020000': port=APT:U ```