Re: remote dwarf info using libunwind

[Alexandre Oliva <aoliva at redhat dot com>]

On Sep 25, 2006, Rick Moseley <rmoseley@redhat.com> wrote:

> Alexandre Oliva wrote:
>> On Sep 17, 2006, Alexandre Oliva <aoliva@redhat.com> wrote:
>>> for  frysk/frysk-imports/libunwind/ChangeLog
>>> from  Alexandre Oliva  <aoliva@redhat.com>

>>> * src/elfxx.c (lookup_symbol): Cope with NULL buf and zero buf_len.
>>> * src/mi/Gget_proc_name.c (intern_string, get_proc_name): Likewise.
>>> * src/hppa/Gget_proc_info.c (unw_get_proc_info): Use it.
>>> * src/x86/Gget_proc_info.c (unw_get_proc_info): Likewise.
>>> * src/x86_64/Gget_proc_info.c (unw_get_proc_info): Likewise.
>>> * doc/unw_get_proc_name.tex: Document NULL buf and zero buf_len.
>>> * doc/unw_create_addr_space.tex (get_proc_name): Likewise.
>>> * doc/unw_get_proc_name.man: Rebuilt.
>>> * doc/unw_create_addr_space.man: Likewise.

> I guess *most* of us were hesitating because we don't feel we are
> qualified to judge the code.

I see.

> If it works ok on your system and does not break any tests I would
> say check it in so the rest of us can test it.

In this case, it's in! :-)

> Thanks for your efforts here, Alex.

My pleasure.  I guess I'll probably disappear from this list at this
point, unless I get further frysk-related assignments.  It was fun to
be around :-)

Please Cc: me explicitly if you find that I broke something or just
would like me to clarify something.  I'm not leaving the mailing list,
but I probably won't pay much attention to it except for stuff in
which I'm explicitly Cc:ed.

Have fun, and keep up the great work,

-- 
Alexandre Oliva         http://www.lsd.ic.unicamp.br/~oliva/
Secretary for FSF Latin America        http://www.fsfla.org/
Red Hat Compiler Engineer   aoliva@{redhat.com, gcc.gnu.org}
Free Software Evangelist  oliva@{lsd.ic.unicamp.br, gnu.org}