Summary

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

Metadata

• Id: 968966918c62abed965871c92c5f8a11a7e2dd1e
• Trac id: 707
• Type: defect
• Reporter: ckeen
• Owner:
• Cc:
• Status: closed
• Component: core libraries
• Estimated difficulty:
• Resolution: worksforme
• Priority: major
• Milestone: 4.9.0
• Version: 4.7.x
• Changetime: 2012-09-24 21:47:48 UTC
• Created: 2011-09-28 21:47:58 UTC
• Keywords:

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?

Changes and comments

[2011-11-03 14:42:54 UTC] felix changed status from new to closed

[2011-11-03 14:42:54 UTC] felix set resolution to worksforme

[2012-09-24 21:47:48 UTC] felix changed milestone from 4.8.0 to 4.9.0

[2012-09-24 21:47:48 UTC] felix wrote:

Milestone 4.8.0 deleted