https://bugs.winehq.org/show_bug.cgi?id=44988
--- Comment #5 from Anastasius Focht focht@gmx.net --- Hello folks,
to check ASLR working on Windows RT device I suggest to get ARM32/ARM64 'Debugging Tools for Windows'. It's part of the Windows 10 SDK.
https://docs.microsoft.com/en-us/windows-hardware/drivers/debugger/debugging...
Follow the instructions from the article:
--- quote --- Getting ARM Debugging Tools for Windows
You can get debugging tools for ARM64 by downloading the Windows 10 SDK (version 10.0.16299 or later). During the installation, select the Debugging Tools for Windows box.
The debugging tools are located in the Debuggers folder in the kit installation directory. The x86 tools are under Debuggers\x86, the ARM32 tools are under Debuggers\ARM, and the ARM64 tools are under Debuggers\ARM64. --- quote ---
After installation on x86 host PC (Windows/Linux+Wine whatever), copy the contents of the 'ARM' directory to the target device.
Start whatever app (unique name) and use 'cdb' to dump modules list/information of the running process:
--- snip --- $ cdb -pv -pn myapp.exe -loga lm.txt -c "lm;q" --- snip ---
('pv' = noninvasive attach mode)
Exit the app and start it another time. Dump info with 'cdb' again.
--- snip --- $ cdb -pv -pn myapp.exe -loga lm.txt -c "lm;q" --- snip ---
The information is written to console and appended to log file 'lm.txt'. The load addresses should be different from the two consecutive runs if the assumption is correct.
Regards