<html>
<head>
<base href="http://llvm.org/bugs/" />
</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 --- - lldb asserts on Linux in ProcessMonitor::GetCrashReasonForSIGSEGV"
href="http://llvm.org/bugs/show_bug.cgi?id=15258">15258</a>
</td>
</tr>
<tr>
<th>Summary</th>
<td>lldb asserts on Linux in ProcessMonitor::GetCrashReasonForSIGSEGV
</td>
</tr>
<tr>
<th>Product</th>
<td>lldb
</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>normal
</td>
</tr>
<tr>
<th>Priority</th>
<td>P
</td>
</tr>
<tr>
<th>Component</th>
<td>All Bugs
</td>
</tr>
<tr>
<th>Assignee</th>
<td>lldb-dev@cs.uiuc.edu
</td>
</tr>
<tr>
<th>Reporter</th>
<td>daniel.malea@intel.com
</td>
</tr>
<tr>
<th>Classification</th>
<td>Unclassified
</td>
</tr></table>
<p>
<div>
<pre>In the testcase TestExprDoesntBlock.py, the inferior sometimes (but not always)
receives a SIGSEGV during expression evaluation. The siginfo structure that
LLDB gets from the kernel has an invalid si_code value (128 == SI_KERNEL).
According to siginfo docs, si_code == SI_KERNEL means that the signal was sent
by the kernel -- but not because a protected or otherwise invalid address was
accessed. Most likely this is happening because of some ptrace() mis-use
somewhere.
While it would be trivial to handle SI_KERNEL and add an appropriate
exit-description string to ProcessMessage.[h|cpp] we want to find out why
SI_KERNEL is being sent to this test case, and why it is not happening always.
Skipping the test case until someone else has time to look at it further.</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>