Re: unwind support for Linux 2.6 vsyscall DSO

[Roland McGrath <roland@redhat.com>]

> I understand.  I would prefer a block-reading interface in the target
> vector (e.g. something similar to target_read_aux_vector as in the patch I
> posted) and a utility function that is an iterator applied to the block.

Note one reason I prefer this is that the utility function is needed
regardless.  If the to_read_aux_vector hook is an iterator, then each
implementation will use this utility function on the contents it's read in.
If the to_read_aux_vector hook returns the whole block, then some of the
callers (not those doing core file writing) will use this utility function
on the contents supplied by the target hook.  The code that needs to be
shared (or duplicated) is the same either way.