reassign 231593 glibc thanks On Mon, Jun 13, 2005 at 09:35:24AM +0200, Steffen Grunewald wrote:
> So since the culprit seems to be some strange handling of two osf_syscall()s > with identical arguments, it looks reasonable to reassign this bug to > libc instead, but nevertheless I'd like to see a pointer in the bug list > for the nis package as well. Would this mean to file a completely new > bug against libc? Please advise... I agree with Steffen's assessment here: NIS isn't doing anything obviously platform specific, no compiler warnings are going off and it works fine on other Debian architectures as far as I can tell. I don't know if the osf_syscall()s in particlar are a problem but I'm fairly sure there's something platform specific that's upsetting glibc. I have seen beheviour like this from older libcs caused by glibc failing to set up thread specific data (that it decides to use off it's own back) but that's just wild guesswork - it's a pretty generic error code that ONC RPC is kicking back. -- "You grabbed my hand and we fell into it, like a daydream - or a fever." -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
