<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 --- - Automated tests are missing for ELF core file support"
   href="http://llvm.org/bugs/show_bug.cgi?id=17237">17237</a>
          </td>
        </tr>

        <tr>
          <th>Summary</th>
          <td>Automated tests are missing for ELF core file support
          </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>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>All Bugs
          </td>
        </tr>

        <tr>
          <th>Assignee</th>
          <td>lldb-dev@cs.uiuc.edu
          </td>
        </tr>

        <tr>
          <th>Reporter</th>
          <td>ashok.thirumurthi@intel.com
          </td>
        </tr>

        <tr>
          <th>Classification</th>
          <td>Unclassified
          </td>
        </tr></table>
      <p>
        <div>
        <pre>As an lldb developer, I would like an automated test for LLDB operation when
run against an ELF core file, so that I know when regressions are introduced.

Note:
* Can run "ulimit -c unlimited" and then build&run
functionalities/inferior-asserting/a.out to generate a core file.
* Can base the tests on existing code in TestInferiorAssert.py that walks the
call stack to inspect frames.


Acceptance Criteria:
* Generate a core file as part of the test rather than checking in a file.
** Delete the generated core file independent of success or failure of the
test.
* Incorporate tests analogous to TestRegisters.py and TestInferiorAssert.py.
* Provide an xfail for AVX register tests.
* Provide an xfail for bugzilla 17227 (incorrect disassembly)</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>