On 2017/3/22 20:46, JonY wrote:
> On 03/22/2017 10:39 AM, Liu Hao wrote:
>> On 2017/3/22 3:59, Jon Turney wrote:
>>> On 21/03/2017 07:43, Ruben Van Boxem wrote:
>>> This value is not guarded in that way in the SDK. I'm not sure why that
>>> might be.
>> I am ok with it if JonY or Kai says it is.
On 03/22/2017 10:39 AM, Liu Hao wrote:
> On 2017/3/22 3:59, Jon Turney wrote:
>> On 21/03/2017 07:43, Ruben Van Boxem wrote:
>> This value is not guarded in that way in the SDK. I'm not sure why that
>> might be.
> I am ok with it if JonY or Kai says it is.
>
I don't see any problems with the
On 21/03/2017 07:43, Ruben Van Boxem wrote:
> Op 21 mrt. 2017 8:07 a.m. schreef "Liu Hao"
> :
>
> On 2017/3/20 20:49, Jon Turney wrote:
>> Windows 10 now has a separate exception for OutputDebugStringW, rather
> than
>> converting the string to ANSI and
Op 21 mrt. 2017 8:07 a.m. schreef "Liu Hao" :
On 2017/3/20 20:49, Jon Turney wrote:
> Windows 10 now has a separate exception for OutputDebugStringW, rather
than
> converting the string to ANSI and raising DBG_PRINTEXCEPTION_C.
>
> (See
On 2017/3/20 20:49, Jon Turney wrote:
> Windows 10 now has a separate exception for OutputDebugStringW, rather than
> converting the string to ANSI and raising DBG_PRINTEXCEPTION_C.
>
> (See
> https://ntquery.wordpress.com/2015/09/07/windows-10-new-anti-debug-outputdebugstringw/)
It can also be
Windows 10 now has a separate exception for OutputDebugStringW, rather than
converting the string to ANSI and raising DBG_PRINTEXCEPTION_C.
(See
https://ntquery.wordpress.com/2015/09/07/windows-10-new-anti-debug-outputdebugstringw/)
Signed-off-by: Jon Turney
---