2014-09-01 13:04 GMT+02:00 Andy Ling <andy.l...@quantel.com>: > Although this doesn't feel right having to keep extending the list of error > codes that are checked. > I'm not sure what else can be done though. Maybe some compile options that > let you choose.
Here is a list of possible error-codes I found: <http://www.vxdev.com/docs/vx55man/vxworks/errno/errnoNumList.html> The value 13 is listed here as EACCES, I really doubt this one should be added: If there really is an access problem, I think that shouldn't be masked. There are two entries that end with _FILE_NOT_FOUND, the other one is: 1310723 0x140003 S_rt11FsLib_FILE_NOT_FOUND This suggests that for VxWorks an additional check for 0x140003 might work if you use the rt11 filesystem (whatever that is .....) Other possible candidates: 2686989 0x29000d S_netDrv_NO_SUCH_FILE_OR_DIR 2949130 0x2d000a S_nfsDrv_NO_SUCH_FILE_OR_DIR 7602186 0x74000a S_cdromFsLib_NO_SUCH_FILE_OR_DIRECTORY The list is not so long, if it helps then it is doable to just add them all. But feedback on behavior on different file systems is crucial, I wouldn't just add all of them blindly. Regards, Jan Nijtmans _______________________________________________ sqlite-users mailing list sqlite-users@sqlite.org http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users
