<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 - Provide a way to lock the current global XRay state"
href="https://bugs.llvm.org/show_bug.cgi?id=37051">37051</a>
</td>
</tr>
<tr>
<th>Summary</th>
<td>Provide a way to lock the current global XRay state
</td>
</tr>
<tr>
<th>Product</th>
<td>XRay
</td>
</tr>
<tr>
<th>Version</th>
<td>unspecified
</td>
</tr>
<tr>
<th>Hardware</th>
<td>PC
</td>
</tr>
<tr>
<th>OS</th>
<td>Linux
</td>
</tr>
<tr>
<th>Status</th>
<td>NEW
</td>
</tr>
<tr>
<th>Severity</th>
<td>enhancement
</td>
</tr>
<tr>
<th>Priority</th>
<td>P
</td>
</tr>
<tr>
<th>Component</th>
<td>Runtime
</td>
</tr>
<tr>
<th>Assignee</th>
<td>dberris@google.com
</td>
</tr>
<tr>
<th>Reporter</th>
<td>dberris@google.com
</td>
</tr>
<tr>
<th>CC</th>
<td>llvm-bugs@lists.llvm.org
</td>
</tr></table>
<p>
<div>
<pre>Currently, with the XRay API functions, it's easy to run into a situation where
a currently installed implementation can be unceremoniously uninstalled. We
should provide a stronger protocol for when we're attempting to select a new
mode, and deprecate specific API functions deemed too dangerous to use.
The protocol should include locking the global state, to not allow for
inadvertently interfering with a currently-installed mode.</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>