Open siltyy opened 4 months ago
no clue.. we were testing with unix like file paths.. not windows drives
UNIX-like file paths, on Windows? I'm a bit confused about what you mean, since I've also tried stuff like /tmp/socket
, /z/tmp/socket
, \\?\GlobalRoot\Global??\Z:\tmp\socket
, \\?\Global\Z:\tmp\socket
, and even just \socket
and /socket
with the socket being at C:\socket
thinking maybe this only supported subdirectories of C:
, and all of them had the same issue.
Z:\tmp\socket
, z:\tmp\socket
, and (with the socket in C:
's root) \socket
are all valid Win32 file paths as defined by https://learn.microsoft.com/en-us/windows/win32/fileio/naming-a-file and should work assuming the comment is correct and the code is working correctly.
When trying to connect to a pathname UNIX domain socket with a program running on Wine, I receive the following error (
ERROR_NO_SUCH_DEVICE
):The test program I'm using is nothing fancy, just
Looking at the output of
strace
, the path I provide is never even checked, and no socket-related operations are done excepting those from Wine itself.Any idea what could be going wrong here, or tips on how to proceed with properly debugging this?
Environment info:
- OS: `Artix Linux Rolling` - Wine: `wine-ge-proton8-4` (reproduces on all other Wine versions I've tried) - uds_windows: `1.1.0` - rustc: `1.76.0 (07dca489a 2024-02-04)` - Build target: `i686-pc-windows-gnu`