<table border="1" cellspacing="0" cellpadding="8">
    <tr>
        <th>Issue</th>
        <td>
            <a href=https://github.com/llvm/llvm-project/issues/59458>59458</a>
        </td>
    </tr>

    <tr>
        <th>Summary</th>
        <td>
            Better disambiguation for "thread jump" destinations
        </td>
    </tr>

    <tr>
      <th>Labels</th>
      <td>
            lldb
      </td>
    </tr>

    <tr>
      <th>Assignees</th>
      <td>
      </td>
    </tr>

    <tr>
      <th>Reporter</th>
      <td>
          labath
      </td>
    </tr>
</table>

<pre>
    Since https://reviews.llvm.org/D133376, clang started emitting epilogue_begin markers in .debug_line. This caused TestThreadJump to fail because jumping to the "return" line in a function like
```
int otherfn()
{
 return 4;
}
```
became ambiguous. After this patch there are two line entries associated with the return line. One has the is_stmt flag, while the other has the epilogue_begin flag. It seems pretty obvious which one should be chosen here, so maybe we could do that automatically.
</pre>
<img width="1px" height="1px" alt="" src="http://email.email.llvm.org/o/eJxsk81u-zYQxJ-Guiz-gkz586BDXMNAe-mhuQdLciUxoUiDu4zhty8oJylaFDBgCTuYHQ5_QmY_RaJB7c5qd2mwyJzyENCgzI1J7jH85aMlmEVurPoXpa9KXzN9erpzG8Ln0qY8KX29bPq-P-yV_g1swDgBC2YhB7R4ER8noJsPaSr0ZmjyERbMH5QZfITWkSnTW_CRWnidPYPFwuTglVhe50zo_ijLDSTBiD6AoXUO72W5VWdJIDOB0jqTlByV1lDNqjfCWKIVnyIE_0Gqu6juRe27r9_66qNAkpnyGJU-Kn36Uh3Ozwd42sJW9efv0eV_nWqyhQAX46eSCrfwMgplkHqoG4qda9JMgJlA7ukZk6JkTwzInKzH2trdyyr9Xv3s5s9IMCOvA89vLIvAGHCqrd9nH2idrEf50f2n9ipv4XcBJloYbplEHpDMp0-Fq4mdIUUCnlMJDgyBnRNThBq77uEECz4MwZ3ArhpX60cBLJIWFG8xhEfbuKF3p_6EDQ2b_aE79v2h2zbzsOuO5Hajc53eWL2nE46u33Yb7McDWa0bP-hO643e6O6oj3rb9tYYe0Q99gc6aTRq29GCPvzw13jmQsPutN0dm4CGAq9Eax2CM0rrynYeqvyXKROrbRc8yz8AN-Il0HAmqbflPD9vEFduxpQrW7KCuEJXAXPE4uOq4KbkMPz7E5m8zMW0Ni1KX-uar79ft5zeyYrS1zU0K31dc_8dAAD__5ezLfM">