<html>
<head>
<base href="https://bugs.documentfoundation.org/">
</head>
<body>
<p>
<div>
<b><a class="bz_bug_link
bz_status_UNCONFIRMED "
title="UNCONFIRMED - CppUnitTester hang on windows 10 machine"
href="https://bugs.documentfoundation.org/show_bug.cgi?id=121228#c5">Comment # 5</a>
on <a class="bz_bug_link
bz_status_UNCONFIRMED "
title="UNCONFIRMED - CppUnitTester hang on windows 10 machine"
href="https://bugs.documentfoundation.org/show_bug.cgi?id=121228">bug 121228</a>
from <span class="vcard"><a class="email" href="mailto:glogow@fbihome.de" title="Jan-Marek Glogowski <glogow@fbihome.de>"> <span class="fn">Jan-Marek Glogowski</span></a>
</span></b>
<pre>An additional missing information is the SolarMutex structure, which holds a
member with the thread id of the process / thread locking the mutex. This
implies you need to post a consistent backtrace of all threads with their TIDs.
Recently there was a commit from Mike using a newer API to handle the Windows
clipboard, which might also help, but still the main problem is to understand
why just you are seeing those assumed deadlocks. It may help to update your
build environment (Cygwin + MSVS) too.</pre>
</div>
</p>
<hr>
<span>You are receiving this mail because:</span>
<ul>
<li>You are the assignee for the bug.</li>
</ul>
</body>
</html>