Menu ▾ ▴

#131 UnlockFileEx (Byte Range locking API) incorrectly uses signed int for lock len

Unstable (example)
closed-fixed
nobody
win32 (Build 218) (1)
5
2016-04-16
2013-09-03
Yury Krasouski
No

Seems like UnlockFileEx has not been completely fixed after resolving issue https://sourceforge.net/p/pywin32/bugs/561/
The win32 api for byte range locks, UnlockFileEx etc specifies unsigned (DWORD) arguments for the length of the lock. The Pywin32 api uses signed int, making it impossible to request some locks that would be allowed using the native wine32 api.

Discussion

  • Mark Hammond

    Mark Hammond - 2016-04-16
    • Description has changed:

    Diff:

    --- old
+++ new
@@ -1,3 +1,2 @@
-
 Seems like UnlockFileEx has not been completely fixed after resolving issue <https://sourceforge.net/p/pywin32/bugs/561/>
 The win32 api for byte range locks, UnlockFileEx etc specifies unsigned (DWORD) arguments for the length of the lock. The Pywin32 api uses signed int, making it impossible to request some locks that would be allowed using the native wine32 api.
    • status: open --> closed-fixed
     

  • Mark Hammond

    Mark Hammond - 2016-04-16

    This was fixed in:

    changeset: 4353:5bab1c62bff6
    user: rupole@spideroak.com
    date: Fri Oct 03 11:51:59 2014 -0400
    summary: Fix DWORD parameters for UnlockFileEx

     

Log in to post a comment.