> Hi!
>
> > > be performed. It is entirely unacceptable for any function, whether
> > > it is in a runtime-library, or is coded by an application, to
> > > pretend that it performed some function that, in fact, it did not.
> >
> > try strcpy(0x12543456, 0x247375394)
> >
> > shock horror it crashes. You passed it a bad pointer. You did the
> > same
>
> It is ok - strcpy either copies memory, or raises SIGSEGV. That's
> ok. It reported error.
>
> About scaling: Yes, it is true that checking for this condition would
> require one mov somewhere inn fclose. Do you think that this is an
> issue?
>
In either case, doesn't that mean it is a c library implementaion issue...
not a kernel issue.
john alvord