[fpc-devel] Weird output from fpGetErrNo

[Marco van de Voort]

In our previous episode, Ewald said:
> I was just writing a little mmapped (that's two `m`'s -- no typo ;-) )
> file stream and thought to do it properly just in case I might fork().
> So I thought to give some advise about memory:

Why not simply use fpgetcerrnp in unit initc?

> I get the most ambiguous results (ENOTTY, ENOENT, which are not even
> documented as being possible error comditions after this call).

What do you see if you strace the resulting binary?