http://bugs.winehq.org/show_bug.cgi?id=20241
--- Comment #2 from mathieu.malaterre@gmail.com 2009-10-04 09:36:32 --- I think some more information on the actual issue can be found here:
http://social.msdn.microsoft.com/forums/en-US/vcgeneral/thread/eb49be0b-2a8c...
... This issue is caused because cygwin does not implement a full login process. It tries to impersonate, but it looks to me as if it does not make the necessary call to LsaLogonUser. As a result, the wrong SID is in the token as the primary user. According to filemon, the debug server calls into secur32, which suggests that it is doing interpretive access control. It finds the service's SID instead of the users SID in some slot in the token that it gets via RPC, and then everything goes downhill from there.
Why VS feels the need to put the PDB access in a separate process under separate access rights is very puzzling, but there it is. ...