[Bug 43379] New: valgrind shows an invalid read in dlls/ntdll/tests/file.c

https://bugs.winehq.org/show_bug.cgi?id=43379

Bug ID: 43379
           Summary: valgrind shows an invalid read in
                    dlls/ntdll/tests/file.c
           Product: Wine
           Version: 2.12
          Hardware: x86
                OS: Linux
            Status: NEW
          Keywords: download, source, testcase, valgrind
          Severity: normal
          Priority: P2
         Component: ntdll
          Assignee: [e-mail]
          Reporter: [e-mail]
      Distribution: ---

==30466== Invalid read of size 1
==30466==    at 0x7BCAD43B: virtual_check_buffer_for_write (virtual.c:1718)
==30466==    by 0x7BC48F48: NtReadFile (file.c:854)
==30466==    by 0x4A47FDE: test_read_write (file.c:3504)
==30466==    by 0x4A4DEE9: func_file (file.c:4288)
==30466==    by 0x4AA25B4: run_test (test.h:603)
==30466==    by 0x4AA2A13: main (test.h:687)
==30466==  Address 0xdeadbeef is on thread 1's stack
==30466==

[Bug 43379] valgrind shows an invalid read in dlls/ntdll/tests/file.c

https://bugs.winehq.org/show_bug.cgi?id=43379

Matteo Bruni  changed:

What    |Removed                     |Added
----------------------------------------------------------------------------
         Resolution|---                         |INVALID
             Status|NEW                         |RESOLVED

--- Comment #1 from Matteo Bruni  ---
That looks intentional. For reference, this is the relevant test code:

status = pNtReadFile(hfile, event, NULL, NULL, &iob, (void*)0xdeadbeef,
sizeof(contents), NULL, NULL);
ok(status == STATUS_ACCESS_VIOLATION, "expected STATUS_ACCESS_VIOLATION, got
%#x\n", status);

[Bug 43379] valgrind shows an invalid read in dlls/ntdll/tests/file.c

https://bugs.winehq.org/show_bug.cgi?id=43379

André H.  changed:

What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|RESOLVED                    |CLOSED
                 CC|                            |[e-mail]

--- Comment #2 from André H.  ---
closing invalid