On Mon Mar 9 17:23:37 2026 +0000, Alexandre Julliard wrote:
I had code to do that when I was working on the Android port, but it wasn't very useful in practice because logcat is a ring buffer of limited size, and the useful information was almost always missing. Downloading a log file to examine off-line was more useful. The intention here is not to rely on logcat as a post-mortem log store. In practice the expected workflow is to collect logs while the application is running.
Android tooling is generally designed around that model. For example Android Studio launches the app itself (either normally or under the debugger) and continuously collects the logcat stream, so the ring buffer size is not a practical limitation because the logs are already being consumed and stored externally. The same approach works from the command line as well, e.g.: ``` adb shell am start -n org.winehq.wine/.WineActivity && adb logcat ... | tee log.txt ``` This allows capturing the entire output stream to a file while the application runs, without any need to collect the file with root or `adb shell run-as` + `cat` approach, making it available immediately on screen and in file on pc. There is also a practical reason not to encourage large persistent log files on-device: with many WINEDEBUG options enabled the log volume can grow very quickly and consume significant storage. Streaming the logs through logcat and capturing them externally avoids that issue. -- https://gitlab.winehq.org/wine/wine/-/merge_requests/10276#note_131614