As reported in https://github.com/llvm/llvm-project/issues/54799, when
using the C APIs unw_init_local(), unw_set_reg(), unw_get_reg()
and unw_step(), sometimes libunwind can erroneously conclude there is
no unwind info available.
This is because the initial call to co->setInfoBasedOnIPRegister() in
unw_init_local() can set _unwindInfoMissing to true, as at that
point there may not yet be unwind info available.
Subsequent calls to unw_set_reg(), with the register parameter set to
UNW_REG_IP, might still be able to find unwind info based on the new
IP value, but it does *not* reset _unwindInfoMissing to false in
those cases, so follow-up calls to unw_step() will erroneously return
UNW_STEP_END immediately.
To fix this, add explicit resets of _unwindInfoMissing to false, in
the various places where setInfoBasedOnIPRegister() actually does find
unwind info.