Experimental Physics and
| |||||||||||||||
|
Kay-Uwe Kasemir wrote:
In vxWorks, errno may be set even when no errors have been returned to application-level code. No vxWorks library routine ever clears the errno variable, thus you should only ever look at its value after some library routine has returned an ERROR status. Some library routines are capable of recovering from errors returned to them by lower level code or may even expect such errors, so just because errno has been set doesn't necessarily mean that anything bad happened. Now it is entirely possible that some code in autosave is not properly looking at some returned status value and is thus missing an error, but if you're looking at errno without explicitly being told to do so (if the above "something fishy" report comes from looking at the ERRNO values output by the 'i' routine for example), you're wasting your time worrying about it. - Andrew -- When a distinguished but elderly scientist states that something is possible, he is almost certainly right. When he states that something is impossible, he is very probably wrong. -- Arthur C. Clarke
| ||||||||||||||
ANJ, 10 Nov 2011 |
·
Home
·
News
·
About
·
Base
·
Modules
·
Extensions
·
Distributions
·
Download
·
· Search · EPICS V4 · IRMIS · Talk · Bugs · Documents · Links · Licensing · |