I was unable to launch remote debugger towards a linux machine from vs 2022. It failed to attach to debugger with no useful message.
Launching vsdbg locally on the linux machine gave the error "fatal error: unable to load resource dll".
Running strace I discovered that it seemed to try access a broken path just before it crashed.
Running winbind my user was a domain user with home path /home/DOMAIN\User. Unable to handle the backslash, vsdbg tried to access a broken path.
I worked around by setting my template homedir in smb.conf to /home/%U instead of including the domain and it started working.
I was unable to launch remote debugger towards a linux machine from vs 2022. It failed to attach to debugger with no useful message.
Launching vsdbg locally on the linux machine gave the error "fatal error: unable to load resource dll".
Running strace I discovered that it seemed to try access a broken path just before it crashed.
Running winbind my user was a domain user with home path /home/DOMAIN\User. Unable to handle the backslash, vsdbg tried to access a broken path.
I worked around by setting my template homedir in smb.conf to /home/%U instead of including the domain and it started working.