A *very* recent Windows build adds more code to the preamble of
RtlGetCurrentDirectory_U() so that the previous heuristic failed to find
the call to the locking routine.
This only affects the 64-bit version of ntdll, where the 0xe8 byte is
now found at offset 40, not the 32-bit version. However, l
Hi Johannes,
On Jan 11 14:21, Johannes Schindelin wrote:
> A *very* recent Windows build adds more code to the preamble of
> RtlGetCurrentDirectory_U() so that the previous heuristic failed to find
> the call to the locking routine.
>
> This only affects the 64-bit version of ntdll, where the 0xe
Hi Corinna,
On Wed, 11 Jan 2017, Corinna Vinschen wrote:
> On Jan 11 14:21, Johannes Schindelin wrote:
> > A *very* recent Windows build adds more code to the preamble of
> > RtlGetCurrentDirectory_U() so that the previous heuristic failed to
> > find the call to the locking routine.
> >
> > Thi
Hi Corinna,
I can see your email on the archive, but, I never received it in my
gmail account (not even in a spam folder). I think the Internet ate
your message.
Yes Windows :). I'm the Program Manager for Windows 10 transports and
IP. Anything in layers 4 or 3. We can help you with network st
