From e3c91c6d524d9bfdb74e9d9bcbdec3c94f216c80 Mon Sep 17 00:00:00 2001 From: Creak Date: Sun, 17 Oct 2021 16:42:51 -0400 Subject: [PATCH] Revert 2827741c994668d6541ff2a3641bc4789677f298...b780d237232fc9260a232220678f940453df1f16 on Log Filters --- Log-Filters.md | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/Log-Filters.md b/Log-Filters.md index d4aa822..c97aeeb 100644 --- a/Log-Filters.md +++ b/Log-Filters.md @@ -12,15 +12,15 @@ Note that `Trace` is *permanently filtered out in non-Debug builds* for performa Class names can be discovered from the log messages themselves. For example, this message is in the class `Service`: ``` -[ 10.285042] Service <Error> core/hle/service/service.h:Service::Interface::SyncRequest:84: unknown/unimplemented function '0x01020000': port=APT:U +[ 10.285042] Service core/hle/service/service.h:Service::Interface::SyncRequest:84: unknown/unimplemented function '0x01020000': port=APT:U ``` A complete list can be found in the source in [log.h](https://github.com/citra-emu/citra/blob/master/src/common/logging/log.h#L36) ## Log Filters -To configure the log filter, you need to change the configuration in `Emulation > Configure... > General > Debug`. Change the `Logging > Global Log Filter` setting. +To configure the log filter, you need to change the configuration in `Emulation > Configure... > General > Debug`. Change the `Logging > Global Log Filter` setting. -The filter string consists of a space-separated list of filter rules, each of the format `<class>:<level>`. `<class>` is a log class name, with subclasses separated using periods. `*` wildcards are allowed and can be used to apply a rule to all classes . `<level>` a severity level name which will be set as the minimum logging level of the matched classes. Rules are applied left to right, with later rules overriding previous ones in the sequence. +The filter string consists of a space-separated list of filter rules, each of the format `:`. `` is a log class name, with subclasses separated using periods. `*` wildcards are allowed and can be used to apply a rule to all classes . `` a severity level name which will be set as the minimum logging level of the matched classes. Rules are applied left to right, with later rules overriding previous ones in the sequence. A few examples of filter rules: - `*:Info` -- Resets the level of all classes to Info.