本文介绍了一个关于ReadDirectoryChangesW函数的小BUG，在特定情况下返回TRUE但bytesReturned为0，导致内存访问违规。通过简单步骤即可复现此问题：主机A共享文件夹，主机B映射并监视该共享文件夹，当主机A粗暴地重命名或删除共享文件夹时，即会出现此BUG。
there are many examples about ReadDirectoyChangesW on Web, but they all have a small bug:
bytesReturned may be zero when ReadDirectoyChangesW()/GetOverlappedResult() return TRUE, in this case,
you will encounter an access violation if read buffer without checking bytesReturned
a simple way to reproduce this bug:
1. host A share a folder, namelly \\hosta\sharefolder
2. host B map \\hosta\sharefolder to Z:, and start a monitor on Z:
3. host A rename/delete sharefolder brutely, then ReadDirectoyChangesW()/GetOverlappedResult() will return TRUE with zero bytesReturned
扫一扫
被折叠的 条评论
为什么被折叠?
到【灌水乐园】发言
