This is the mail archive of the
mailing list for the Cygwin project.
Re: Question about flock - potential memory corruption?
- From: Qian Hong <fracting at gmail dot com>
- To: cygwin <cygwin at cygwin dot com>
- Date: Tue, 8 Sep 2015 02:41:53 +0800
- Subject: Re: Question about flock - potential memory corruption?
- Authentication-results: sourceware.org; auth=none
- References: <CALd+sZRo_Nyv=adF5DeeHiShJsxGD+KUPqkDMKb3q47a2Nm=8Q at mail dot gmail dot com>
- Reply-to: fracting at gmail dot com
I was still not able to make valgrind display Cygwin symbols, so I
manually translate the address to line this time.
$ uname -a
CYGWIN_NT-5.1 2.2.1(0.289/5/3) 2015-08-20 11:40 i686 Cygwin
==29863== Conditional jump or move depends on uninitialised value(s)
==29863== at 0x7BC82768: RtlGetOwnerSecurityDescriptor (sec.c:740)
==29863== by 0x7BC92356: NTDLL_create_struct_sd (sync.c:96)
==29863== by 0x7BC92E10: NtCreateEvent (sync.c:294)
==29863== by 0x6107B937: ???
==29863== by 0x61304697: ???
Here 0x6107b937 is the call to NtCreateEvent() inside
(I can't explain what the address 0x61304697 means, it seems a bit
weird to me, not sure if it is valgrind related)
Related Wine source code:
According to valgrind, lpsd->Control in
RtlGetOwnerSecurityDescriptor() is uninitialized, which means
NtCreateEvent(,attr,) is not initialized, that's why I'm looking at
create_lock_obj_attr() and everyone_sd(). It seems after
create_lock_obj_attr returned the memory allocated by alloca() is
gone, which cause the valgrind warnings, also cause the random
If there is any further information required I'm glad to test and provide.
Any comments are great appreciated!
Problem reports: http://cygwin.com/problems.html
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple