Re: remote dwarf info using libunwind

[Tom Tromey <tromey at redhat dot com>]

Alexandre> Yes, sorry.  I failed to refresh the patch file after
Alexandre> renaming the method.  I'm not sure whether I missed any
Alexandre> other change, so here's the patch generated out of what I
Alexandre> actually tested.

I updated, applied this and built frysk.  I'm using x86 FC5.  Then I tried
my 'fdtrace' program.

I get somewhat weird results:

    opsy. ./frysk-core/frysk/bindir/fdtrace ../Closer
    bad close() call at:
    val = frysk.rt.StackFrame@157de0; in function:  (Unknown file at line 0)
    val = frysk.rt.StackFrame@157db0; in function:  (Unknown file at line 0)
    val = frysk.rt.StackFrame@157d80; in function:  (Unknown file at line 0)

This is an improvement since stack tracing used to just crash.  And it
is clearly doing something correctly, because that looks like a
reasonable number of stack frames.

But, it isn't finding the function name, file name, or line number
properly.

I've appended fdtrace.java... it is just a naively hacked copy of
ftrace.  'Closer' is just a program that does a sequence of invalid
closes:

    #include <unistd.h>
    #include <stdio.h>
    int main() {
      close(73);
      close(74);
      return 0;
    }

Tom

Attachment: fdtrace.java
Description: fdtrace.java