matt@theBachChoir.org.uk said:
> but his example fcloses a file which was not opened. This isn't
> "further access".
He said that it arises from a program that closes a file twice.
> Is it difficult for Linux to spot the the file isn't open and return
> EBADF? What does POSIX have to say about this? IMHO making it easier
> to port your programs to Linux (and behaving a little more sanely :)
> is worth a couple of extra bytes of anyone's kernel.
If it got as far as the kernel, it'd get EFAULT rather than SIGSEGV. It's a
glibc issue if anything.
-- dwmw2- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.rutgers.edu Please read the FAQ at http://www.tux.org/lkml/
This archive was generated by hypermail 2b29 : Sat Jul 15 2000 - 21:00:16 EST