[Bug 49425] "wine" command changes the working directory when given a path to a .exe
WineHQ Bugzilla
wine-bugs at winehq.org
Mon Jun 22 09:13:26 CDT 2020
https://bugs.winehq.org/show_bug.cgi?id=49425
François Gouget <fgouget at codeweavers.com> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |fgouget at codeweavers.com
--- Comment #6 from François Gouget <fgouget at codeweavers.com> ---
This also partially breaks the TestBot: when one manually submits a job to run
in the 64-bit Wine, the TestBot chdirs() to c:\ where the test executable is
and then runs ".../wine TestLauncher64.exe foo_test.exe xxx". But wine resets
the current directory to / before hitting TestLauncher's main() which then
cannot do its executable dependency checks.
Interestingly this is specific to the 32-bit -> 64-bit cross-calls:
wine foo32.exe -> current directory is preserved
wine foo64.exe -> current directory is reset to /
wine64 foo64.exe -> current directory is preserved
This is also why the pure 32-bit and 32-bit WoW tests still run fine.
The patches submitted to wine-devel also work but for a different reason:
instead of TestLauncher those go through winetest.exe in a way that does not
depend on the current directory.
--
Do not reply to this email, post in Bugzilla using the
above URL to reply.
You are receiving this mail because:
You are watching all bug changes.
More information about the wine-bugs
mailing list