<html>
<head>
<base href="https://bugs.llvm.org/">
</head>
<body><table border="1" cellspacing="0" cellpadding="8">
<tr>
<th>Bug ID</th>
<td><a class="bz_bug_link
bz_status_NEW "
title="NEW - Use of PrintStackTraceOnErrorSignal may cause hang on Windows"
href="https://bugs.llvm.org/show_bug.cgi?id=34691">34691</a>
</td>
</tr>
<tr>
<th>Summary</th>
<td>Use of PrintStackTraceOnErrorSignal may cause hang on Windows
</td>
</tr>
<tr>
<th>Product</th>
<td>libraries
</td>
</tr>
<tr>
<th>Version</th>
<td>trunk
</td>
</tr>
<tr>
<th>Hardware</th>
<td>PC
</td>
</tr>
<tr>
<th>OS</th>
<td>Windows NT
</td>
</tr>
<tr>
<th>Status</th>
<td>NEW
</td>
</tr>
<tr>
<th>Severity</th>
<td>normal
</td>
</tr>
<tr>
<th>Priority</th>
<td>P
</td>
</tr>
<tr>
<th>Component</th>
<td>Support Libraries
</td>
</tr>
<tr>
<th>Assignee</th>
<td>unassignedbugs@nondot.org
</td>
</tr>
<tr>
<th>Reporter</th>
<td>gbreynoo@gmail.com
</td>
</tr>
<tr>
<th>CC</th>
<td>llvm-bugs@lists.llvm.org
</td>
</tr></table>
<p>
<div>
<pre>Use of PrintStackTraceOnErrorSignal (/Support/Signals.h) can cause hangs due to
the call of MiniDumpWriteDump when an exception is unhandled.
>From the MiniDumpWriteDump description:
"MiniDumpWriteDump should be called from a separate process if at all possible,
rather than from within the target process being dumped. This is especially
true when the target process is already not stable. For example, if it just
crashed. A loader deadlock is one of many potential side effects of calling
MiniDumpWriteDump from within the target process"
<a href="https://msdn.microsoft.com/en-us/library/windows/desktop/ms680360(v=vs.85).aspx">https://msdn.microsoft.com/en-us/library/windows/desktop/ms680360(v=vs.85).aspx</a></pre>
</div>
</p>
<hr>
<span>You are receiving this mail because:</span>
<ul>
<li>You are on the CC list for the bug.</li>
</ul>
</body>
</html>