https://software.intel.com/fr-fr/forums/topic/372572/feed
frI think we have a fix forhttps://software.intel.com/fr-fr/comment/1726574#comment-1726574
<a id="comment-1726574"></a>
<div class="field field-name-comment-body field-type-text-long field-label-hidden"><div class="field-items"><div class="field-item even" property="content:encoded"><p>I think we have a fix for this but we would like to verify it on your code if possible. Do you have a sample you could send me where the failure is manifest?</p>
</div></div></div>Fri, 01 Mar 2013 16:06:14 +0000mad\jvoliviecomment 1726574 at https://software.intel.comThe bug you encountered hashttps://software.intel.com/fr-fr/comment/1726144#comment-1726144
<a id="comment-1726144"></a>
<div class="field field-name-comment-body field-type-text-long field-label-hidden"><div class="field-items"><div class="field-item even" property="content:encoded"><p>The bug you encountered has been found recently in our internal testing. It is caused by a mishandling of InitializeCriticalSectionEx in the tool when the CRITICAL_SECTION in question happens to be at the same address as a previously intialized SRW lock and, therefore, it gets misinterpreted on acquire as an SRW lock. </p>
<p>The best solution will be to get you an updated version of Inspector that has this bug fixed (which doesn't exist at present). In the meantime, a workaround would be to refrain, if possible, from using InitializeCriticalSectionEx and instead use one of the other intialization routines. This may not be possible considering that the initialization in question may not have actually originated from your code but without an update, it is the best advice I can give.</p>
<p>I apologize for the inconvenience this has caused you. </p>
</div></div></div>Tue, 26 Feb 2013 17:02:12 +0000mad\jvoliviecomment 1726144 at https://software.intel.com