<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 - Revisit the failure path for Process::Resume() to avoid leaking Stopped->Running->Stopped events"
   href="https://bugs.llvm.org/show_bug.cgi?id=34594">34594</a>
          </td>
        </tr>

        <tr>
          <th>Summary</th>
          <td>Revisit the failure path for Process::Resume() to avoid leaking Stopped->Running->Stopped events
          </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>enhancement
          </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@lists.llvm.org
          </td>
        </tr>

        <tr>
          <th>Reporter</th>
          <td>mosescu@google.com
          </td>
        </tr>

        <tr>
          <th>CC</th>
          <td>llvm-bugs@lists.llvm.org
          </td>
        </tr></table>
      <p>
        <div>
        <pre>Jim Ingham re. <a href="https://reviews.llvm.org/D37651">https://reviews.llvm.org/D37651</a> :

"This looks okay for now.  It will end up sending a Running & then a Stopped
event.  That's a little awkward, but that happens in the ordinary course of
debugging anyway so it shouldn't freak anybody out.

It would be better to find a place where this can be fixed before we send the
running event, but that's going to take more thinking, and I don't see that
desire should block this patch.  But can you file another PR to go figure out
how to fix this closer to the source, so we don't forget to fix this next time
we're in the bowels of the process event code?"</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>