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

    <tr>
        <th>Summary</th>
        <td>
            LLDB cannot recognise assertion failures on new glibcs
        </td>
    </tr>

    <tr>
      <th>Labels</th>
      <td>
            new issue
      </td>
    </tr>

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

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

<pre>
    New glibcs (circa 2.34) have an extra frame on top of the assert stacks. This frame belongs to the `__pthread_kill_implementation` function, but (as the name implies) this is a private implementation detail. In fact, if the user does not have debug info for the c library, then lldb will not even know the name of that function. frames below that belong to `raise` and `abort` (public functions), but the current lldb frame recogniser infrastructure only uses the topmost frame, which makes fixing this not entirely trivial.
</pre>
<img width="1px" height="1px" alt="" src="http://email.email.llvm.org/o/eJxFUsGOozAM_Rq4WIvaFDr0wGFnR5VWGu1p75WBANmGBCWmnf792mGmIyKRxPbLe89uff9o_ug7jNa0XYRM1Z0JHYIqDmWmTjDhTQM60B8UEIaAswbvgPwCfgCaOBijDgSRsLvGAv5OJn7mtdp6N0ZOTonZcXe5LDQFjf3laqy9mHmxetaOkIx3HIdhdV3aq1_QriR8MKZqJ4hSYHQUYiTv8EJYgrkhbcFvNOg1obEF_HYwYEeCaDbGKxOG3usIztOmsNftOoJxg4fBh5TVAVsSMDykki8cWNu3cGfiqU7f-Orq_P2bXnIE6ami2IyIyYn7FttMEU9Yb0ATtehG18sZWx9Izqx7WVtruieWiP5yJdFbQ2CtG6nN76A7Pzoj6lhJwEhh7WgN0jH7ENmbldy82UfaqgTzPplughmvnDCYDyP8xN4k05EJmsuJbTZoi7xvDv3pcMKcDFndvL-_vUKHTpKfDD6nQvowcBeYQ5Sxcc9Jy9dgm4loidnhZ6bOvEZD09oWnZ_5YO3t6_djCf6flg6eTYyrtP9cHfdlmU8N9jjs1f4F22rYnRRf9yd1PNb6Zb_jr84tsuGxyarXTCl5PkHwPqvectOonVK7o9ozWnWoi7I81aqtsNLHPdZ1mZU7PcsUCY_ChzEPTaLE0xI5aE2k-B1k0WZ0WqfnGB9XmjxXYIs05enlJjH_Dw4LMGQ">