OpenPunk/citra
1
0
Fork 0
mirror of https://github.com/citra-emu/citra.git synced 2024-11-25 16:50:15 +00:00
Code Issues Projects Releases Wiki Activity

Updated Log Filters (markdown)

Pengfei Zhu 2018-12-16 11:52:39 +08:00
parent f8509186a9
commit 2827741c99
1 changed files with 4 additions and 2 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

6
Log-Filters.md

@ -14,11 +14,13 @@ Class names can be discovered from the log messages themselves. For example, thi
``` ```
[ 10.285042] Service <Error> core/hle/service/service.h:Service::Interface::SyncRequest:84: unknown/unimplemented function '0x01020000': port=APT:U [ 10.285042] Service <Error> core/hle/service/service.h:Service::Interface::SyncRequest:84: unknown/unimplemented function '0x01020000': port=APT:U
``` ```
Otherwise, 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) 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 ## Log Filters
To configure the log filter, edit the configuration file (either `qt-config.ini` or `sdl2-config.ini`) and change the `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. 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.
A few examples of filter rules: A few examples of filter rules:
- `*:Info` -- Resets the level of all classes to Info. - `*:Info` -- Resets the level of all classes to Info.