re: NetBSD Bad address failure (was Re: [HACKERS] Third call for platform testing)

2001-04-16 Thread matthew green
yes, this is a bug in netbsd-current that was introduced with about 5 month ago with the new unified buffer cache system. it has been fixed. thanks. From: Chuck Silvers [EMAIL PROTECTED] To: [EMAIL PROTECTED] Subject: CVS commit: syssrc Date: Mon, 16 Apr 2001 17:37:44 +0300 (EEST)

Re: NetBSD Bad address failure (was Re: [HACKERS] Third call for platform testing)

2001-04-14 Thread Tom Ivar Helbekkmo
Tom Lane [EMAIL PROTECTED] writes: I think this is indisputably a bug in (some versions of) NetBSD. I forgot to mention a possible contributing factor: the files involved were NFS-mounted, in the case I was looking at. So this may be an NFS problem more than a NetBSD problem. Anyone

Re: NetBSD Bad address failure (was Re: [HACKERS] Third call for platform testing)

2001-04-14 Thread Tom Lane
Tom Ivar Helbekkmo [EMAIL PROTECTED] writes: I can verify, that with NetBSD-current on sparc, your test code works the way you want it to on local disk, but fails (in the way you've observed), if the target file is on an NFS-mounted file system. FWIW, the test program succeeds (no error)

Re: NetBSD Bad address failure (was Re: [HACKERS] Third call for platform testing)

2001-04-13 Thread Tom Lane
I wrote: I think this is indisputably a bug in (some versions of) NetBSD. If I can seek past the end of file, read() shouldn't consider it a hard error to read there --- and in any case, EFAULT isn't a very reasonable error code to return. Since it seems not to be a widespread problem, I'm