Re: is UNW_REMOTE_ONLY in-dispensable fro Frysk

[Alexandre Oliva <aoliva at redhat dot com>]

On Sep 11, 2006, Andrew Cagney <cagney@redhat.com> wrote:

> Wu Zhou wrote:
>> UNW_REMOTE_ONLY is causing some trouble for us to work on ppc64
>> porting of libunwind.  I am thinking over if it is in-dispensable
>> for Frysk.
> I don't think it is in-dispensable, however, it is correct on
> principle - this code has no need to do native unwinding - and it lets
> us avoid a number of ongoing issues where the native-unwind defined
> symbols that clashed with libgcj.

Actually, we absolutely must do away with it.  A number of libunwind
internal routines mmap or otherwise copy stuff from the target process
and then decode it locally, for which it needs functional
local_address_space callbacks.  One might try to qualify that as a
bug, but unless we're willing to fix that by rewriting a lot of code,
we'll be better off simply removing this local hack.  That's what the
patch I just posted (in the thread remote dwarf info using libunwind)
does, and this is the reason for the change, that I think I failed to
explain there.

> Perhaps something to discuss on the libunwind list?

Probably not, given that it's a local change.

-- 
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}