Re: remote dwarf info using libunwind

[Mike Cvet <mcvet at redhat dot com>]

On Wed, 2006-09-13 at 06:43 -0300, Alexandre Oliva wrote:
> It still fails to print line numbers for main and for kernel vdso
> syscalls and their callers, but other than that, it's much better than
> before.
> The patch is not quite ready for public consumption (still missing a
> ChangeLog, for one), but I thought I'd post it for people who'd like
> to use it as is.
> 
> My plan is to use the same code htat unw_get_proc_name() uses to
> locate the procedure info and use that in unw_get_proc_info as a
> fallback, but that will have to wait until I get some sleep.
> 
> I actually took a stab at dyn_list_addr, but I can't quite figure out
> whether this is even to be found somewhere in the memory map of the
> target process.  At first I thought it was supposed to be the dynamic
> loader's linked list of dynamic libs, but that's not it.  Does anyone
> know?
> 

According to upstream, all the dyn_list_* stuff is to handle
dynamically-generated code only. So, probably shouldn't have an effect
on what we're doing currently anyway.

- Mike