Re: remote dwarf info using libunwind

[Alexandre Oliva <aoliva at redhat dot com>]

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

> Do any of the _UPT_* calls you added interact with either /proc or ptrace?

Nope, that was the point of the split.  I suppose we could still use
libunwind-ptrace's get_proc_name, and only use our Java interfaces for
stuff that actually interacts with the target process.  I wonder if
this would fix Tom's reported bug.

> Why is the cpu specific library required?
> + ../frysk-imports/libunwind/src/libunwind-$(libunwind_cpu).a

-ENOCLUE, it was already there:

-GEN_GCJ_LDADD += ../frysk-imports/libunwind/src/libunwind-$(libunwind_cpu).a
+GEN_GCJ_LDADD += ../frysk-imports/libunwind/src/libunwind-ptrace.a \
+		 ../frysk-imports/libunwind/src/libunwind-$(libunwind_cpu).a

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