Opened 9 years ago

Closed 9 years ago

Last modified 8 years ago

#707 closed defect (worksforme)

##sys#file-info needs to signal an error if the fstat syscall goes bad

Reported by: Christian Kellermann Owned by:
Priority: major Milestone: 4.9.0
Component: core libraries Version: 4.7.x
Keywords: Cc:
Estimated difficulty:

Description

I think it is bad style to ignore the errno error signalling mechanism when doing syscalls. Bug #706 shows that this can result in serious mischief.

##sys#file-info is the first culprit that I have identified, but I suspect all runtime calls lack a error propagation mechanism.

Maybe a more general approach on how to do this is needed.
At the time of writing this I am favoring raising exn i/o conditions for the exceptional cases. Also would these calls be reentrant?

Change History (2)

comment:1 Changed 9 years ago by felix winkelmann

Resolution: worksforme
Status: newclosed

comment:2 Changed 8 years ago by felix winkelmann

Milestone: 4.8.04.9.0

Milestone 4.8.0 deleted

Note: See TracTickets for help on using tickets.