N-archive/citra
1
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity

Replace '<' and '>' with their respective HTML entities

Creak 2021-10-17 16:41:25 -04:00
parent 069deaa9ab
commit b780d23723
1 changed files with 3 additions and 3 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

6
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 &lt;Error&gt; 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 &gt; Configure... &gt; General &gt; Debug`. Change the `Logging &gt; 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 `&lt;class&gt;:&lt;level&gt;`. `&lt;class&gt;` is a log class name, with subclasses separated using periods. `*` wildcards are allowed and can be used to apply a rule to all classes . `&lt;level&gt;` 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.