mirror of
https://github.com/ARMSX2/ARMSX3.git
synced 2026-08-24 16:58:52 -07:00
jpolo1224
0cc115af48
The previous commit read driver_env.txt before the log file was opened, so the one thing worth knowing -- whether the option was applied -- was written into a listener that did not exist yet and then thrown away when the log rotated. Move the read to just after the log file is created and report each option by reading it back rather than echoing what was meant to be set. There is no other honest confirmation available: /proc/<pid>/environ is the snapshot taken at exec and never reflects a runtime setenv, and Mesa's own logging goes to stderr, which Android discards. Still long before any Vulkan instance exists, which is the only ordering Mesa cares about.