On Apr 14 16:24, Pierre A. Humblet wrote:
I can see why would one think this is a bug, but it was meant
to be that way. Having a wrong gid can make seteuid fail.
Perhaps we could print the new and current uids and the current
gid to cover all cases.
Yep, that's how I did it already locally.
I can see why would one think this is a bug, but it was meant
to be that way. Having a wrong gid can make seteuid fail.
Perhaps we could print the new and current uids and the current
gid to cover all cases.
Pierre
At 01:59 PM 4/14/2005 +0900, Kazuhiro Fujieda wrote:
I'd submit a trivial patch
I'd submit a trivial patch after a long time.
2005-04-14 Kazuhiro Fujieda [EMAIL PROTECTED]
* syscalls.cc (setuid32): Correct debugging output.
Index: syscalls.cc
===
RCS file: /cvs/src/src/winsup/cygwin/syscalls.cc,v
