On 09/04/2012 06:17 PM, Bryce McKinlay wrote: > On Tue, Sep 4, 2012 at 6:12 PM, Andrew Haley <a...@redhat.com> wrote: > >>> He's also planning to use it for libgo, and other gcc runtime libs >>> have indicated interest. It doesn't have to work on all platforms, and >>> I can't see how it would be any less portable than addr2line! >> >> I certainly can. Maybe once it's shaken-down so it's at least as >> robust as what we have now it'll be OK. I suspect it hasn't had much >> testing with, for example, unwinding through signal handlers. > > libgcj wouldn't actually use it for unwinding, we already have all > that. We'd just use it to read DWARF debug info and give us the source > code line numbers.
OK, as long as that's all it does. I think I was perhaps a bit misled by its description of "a stack backtrace library". It certainly looks like a nicer approach than addr2line, but is going to be much less well-ported. I guess we'll see how it goes. Andrew.
