http://bugs.winehq.org/show_bug.cgi?id=26119
Summary: kernel32/pipe tests show some valgrind warnings Product: Wine Version: 1.3.13 Platform: x86 OS/Version: Linux Status: NEW Keywords: download, source, testcase Severity: minor Priority: P2 Component: kernel32 AssignedTo: wine-bugs@winehq.org ReportedBy: austinenglish@gmail.com
Created an attachment (id=33293) --> (http://bugs.winehq.org/attachment.cgi?id=33293) valgrind log
Syscall param writev(vector[...]) points to uninitialised byte(s) at writev (in /lib/libc-2.11.2.so) by send_request (server.c:209) by wine_server_call (server.c:290) by NTDLL_wait_for_multiple_objects (sync.c:1118) by NtWaitForMultipleObjects (sync.c:1162) by NtWaitForSingleObject (sync.c:1171) by server_ioctl_file (file.c:1276) by NtFsControlFile (file.c:1523) by ConnectNamedPipe (sync.c:1589) by serverThreadMain1 (pipe.c:425) by ??? (signal_i386.c:2473) by call_thread_entry_point (signal_i386.c:2499) by start_thread (thread.c:404) by start_thread (in /lib/libpthread-2.11.2.so) by clone (in /lib/libc-2.11.2.so) Address 0x7f43e42c is on thread 1's stack Uninitialised value was created by a stack allocation at ConnectNamedPipe (sync.c:1575)
and several possibly memory leaks.
http://bugs.winehq.org/show_bug.cgi?id=26119
--- Comment #1 from Austin English austinenglish@gmail.com 2012-09-26 14:16:35 CDT --- ==27927== Thread 3: ==27927== Syscall param writev(vector[...]) points to uninitialised byte(s) ==27927== at 0x426C696: writev (writev.c:56) ==27927== Address 0x7ffd2d6c is on thread 1's stack ==27927== Uninitialised value was created by a stack allocation ==27927== at 0x7B871723: ConnectNamedPipe (sync.c:1578) ==27927== { <insert_a_suppression_name_here> Memcheck:Param writev(vector[...]) fun:writev }
still present.
https://bugs.winehq.org/show_bug.cgi?id=26119
Austin English austinenglish@gmail.com changed:
What |Removed |Added ---------------------------------------------------------------------------- Attachment #33293|0 |1 is obsolete| |
--- Comment #2 from Austin English austinenglish@gmail.com --- Created attachment 48235 --> https://bugs.winehq.org/attachment.cgi?id=48235 valgrind log in wine-1.7.17-42-g24c5728
https://bugs.winehq.org/show_bug.cgi?id=26119
Austin English austinenglish@gmail.com changed:
What |Removed |Added ---------------------------------------------------------------------------- Blocks| |36071
https://bugs.winehq.org/show_bug.cgi?id=26119
--- Comment #3 from Austin English austinenglish@gmail.com --- A similar issue in hlink/tests/hlink.c: ==11822== Thread 3: ==11822== Syscall param writev(vector[...]) points to uninitialised byte(s) ==11822== at 0x4E9528CC: writev (in /usr/lib/libc-2.18.so) ==11822== by 0x7BC7FE6F: send_request (server.c:213) ==11822== by 0x7BC80001: wine_server_call (server.c:294) ==11822== by 0x7BC80E6E: server_select (server.c:591) ==11822== by 0x7BC8A6F6: NtWaitForMultipleObjects (sync.c:863) ==11822== by 0x7BC8A746: NtWaitForSingleObject (sync.c:872) ==11822== by 0x7BC47912: server_ioctl_file (file.c:1375) ==11822== by 0x7BC48312: NtFsControlFile (file.c:1623) ==11822== by 0x7B8796BF: ConnectNamedPipe (sync.c:1608) ==11822== by 0x469EF26: listen_thread (rpc_transport.c:131) ==11822== by 0x7BC87137: ??? (signal_i386.c:2571) ==11822== by 0x7BC87180: call_thread_func (signal_i386.c:2630) ==11822== by 0x7BC87115: ??? (signal_i386.c:2571) ==11822== by 0x7BC8E560: start_thread (thread.c:428) ==11822== by 0x4EA7BD89: start_thread (in /usr/lib/libpthread-2.18.so) ==11822== by 0x4E95CA0D: clone (in /usr/lib/libc-2.18.so) ==11822== Address 0x51be59c is on thread 1's stack ==11822== Uninitialised value was created by a stack allocation ==11822== at 0x7B8795C0: ConnectNamedPipe (sync.c:1594) ==11822==
https://bugs.winehq.org/show_bug.cgi?id=26119
Austin English austinenglish@gmail.com changed:
What |Removed |Added ---------------------------------------------------------------------------- Keywords| |valgrind
https://bugs.winehq.org/show_bug.cgi?id=26119
joaopa jeremielapuree@yahoo.fr changed:
What |Removed |Added ---------------------------------------------------------------------------- CC| |jeremielapuree@yahoo.fr
--- Comment #4 from joaopa jeremielapuree@yahoo.fr --- Created attachment 65595 --> https://bugs.winehq.org/attachment.cgi?id=65595 console output
Looks like this bug is fixed in wine-4.19 (see the attached console output). Can an administrator close this bug as FIXED?
https://bugs.winehq.org/show_bug.cgi?id=26119
Austin English austinenglish@gmail.com changed:
What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |RESOLVED Resolution|--- |FIXED
--- Comment #5 from Austin English austinenglish@gmail.com --- (In reply to joaopa from comment #4)
Created attachment 65595 [details] console output
Looks like this bug is fixed in wine-4.19 (see the attached console output). Can an administrator close this bug as FIXED?
Yeah, I'm not seeing this either in wine-4.20-213-gddec23013e
https://bugs.winehq.org/show_bug.cgi?id=26119
Alexandre Julliard julliard@winehq.org changed:
What |Removed |Added ---------------------------------------------------------------------------- Status|RESOLVED |CLOSED
--- Comment #6 from Alexandre Julliard julliard@winehq.org --- Closing bugs fixed in 4.21.
-
wine-bugs＠winehq.org -
WineHQ Bugzilla