This is the mail archive of the
mailing list for the Cygwin project.
RE: Permission denied with makeinfo from texinfo-4.0
- To: 'Mumit Khan' <khan at NanoTech dot Wisc dot EDU>, cygwin at sourceware dot cygnus dot com
- Subject: RE: Permission denied with makeinfo from texinfo-4.0
- From: Heribert Dahms <heribert_dahms at icon-gmbh dot de>
- Date: Tue, 4 Apr 2000 22:14:46 +0200
- Cc: Christopher Faylor <cgf at cygnus dot com>
hmm, I don't know Win32 enough, but what about
checking for ERROR_NOACCESS and >32k,
then retry with 0 (or something small) to see if
ERROR_NOACCESS persists? Could be a problem
for e.g. tape access with fixed block sizes...
Bye, Heribert (email@example.com)
> -----Original Message-----
> From: Mumit Khan [SMTP:khan@NanoTech.Wisc.EDU]
> Sent: Sunday, April 02, 2000 22:59
> To: firstname.lastname@example.org
> Cc: Christopher Faylor
> Subject: Re: Permission denied with makeinfo from texinfo-4.0
> On Wed, 15 Mar 2000, Chris Faylor wrote:
> > This sounds correct to me. Passing what is essentially a bogus
> > for the buffer length is just wrong. At the very least, it's
> subject to
> > problems if the file size changes while you're reading it.
> > this is an unusual occurrence but why not program for something like
> > and fail gracefully rather than core dumping?
> fyi, the makeinfo bug is caused by a (undocumented of course) bug in
> ReadFile routine.
> Here's what David Korn says when it showed up in UWIN as well:
> Yet some more bizarre undocumented win32 behavior. If you call the
> Win32 ReadFile() function with size greater than 32K, and you are
> at the end of file, it does not return successfully with 0 bytes as
> you would expect, but fails with ERROR_NOACCESS.
> This should be fixed in the runtime, but I have to find a reliable way
> to detect this (since we have to differentiate between this buggy
> behaviour and other legitimate causes of ERROR_NOACCESS).
> Want to unsubscribe from this list?
> Send a message to email@example.com
Want to unsubscribe from this list?
Send a message to firstname.lastname@example.org