While reading the newest codes, I found several suspicious codes that could be potential error handling bugs.
setsockopt is called without checking its return value in the following functions : TclSockMinimumBuffers, nt_loadWinSock.
chdir is called without checking its return value in the following functions : restore_wd, chdir_safer, pending_main, resolve_tags, abort_patch, gnupatch_main, export_main, sane, converge_hash_files.
setsockopt is called without checking its return value in sccs_gone.
move_remote is called without checking its return value in the following functions : free_slot, merge, copy_to_resync, converge
sccs_clean is called without checking its return value in converge.
mdbm_store is called without checking its return value in shrink_main.
I understand that some of them were intentionally removed for the purpose of simplifying your code. But I'm listing them in case you want to maintain them in the future.
While reading the newest codes, I found several suspicious codes that could be potential error handling bugs.
setsockopt is called without checking its return value in the following functions : TclSockMinimumBuffers, nt_loadWinSock.
chdir is called without checking its return value in the following functions : restore_wd, chdir_safer, pending_main, resolve_tags, abort_patch, gnupatch_main, export_main, sane, converge_hash_files.
setsockopt is called without checking its return value in sccs_gone.
move_remote is called without checking its return value in the following functions : free_slot, merge, copy_to_resync, converge
sccs_clean is called without checking its return value in converge.
mdbm_store is called without checking its return value in shrink_main.
I understand that some of them were intentionally removed for the purpose of simplifying your code. But I'm listing them in case you want to maintain them in the future.