Re: [libunwind] remote unwinding and dynamically-generated code

[Todd L Miller]

> Todd> int dyn_register( unw_addr_space_t as, unw_word_t addr, void *
> Todd> arg );
>
> Todd> where addr is the address of the unw_dyn_info_t in the addess
> Todd> space 'as', or should it be something else, perhaps another
> Todd> function in the accessors?
>
> The interface looks fine to me, but since it'll need to be implemented
> as part of libunwind-ptrace, the name should be _UPT_dyn_register()
> (and the prototype should go in include/libunwind-ptrace.h).

        I'm not convinced it needs to use ptrace() explicitly; my
intention was to use access_mem()* from the addr_space's accessors in a
machine-independent routine, so that we _know_ the local and remote
registration routines are in synch (since they're the same).

- Todd

* I'm not sure why the fetch() routines are defined in include/remote.h;
  it may just be because a situation where oblivousness to local or
  remote memory hadn't come up before.