Re: [libunwind] suggest adding unw_init_local_accessors

[David Mosberger]

>>>>> On Wed, 11 Dec 2002 16:08:03 -0800, Mark Young <address@hidden> said:

  Mark> As presently implemented, an UNW_ENOINFO error from
  Mark> unw_init_local, unw_init_remote, or unw_step is a
  Mark> forward-looking statement that the unwinder does not know how
  Mark> to take the _next_ unwind step. It does not necessarily mean
  Mark> that the cursor's current frame state data is inaccurate.

It does mean that the cursor's frame state is incomplete: the info
from the proc_info will be missing (start_ip, end_ip, gp, lsda, and
personality routine address).

What we could do is evaluate the ia64_make_proc_info() in a lazy
fashion, i.e., only in response to a call to unw_get_proc_info() or
when it is needed as part of unw_step().  That would get rid of the
call to ia64_make_proc_info() in unw_{local,remote}_init().

        --david