Hello, I came across libunwind recently and it looks like it would fit our need just perfectly. What we need is to be able to get backtraces without the need to instrument function calls (which is what we are currently doing).
So I implemented a small proof-of-concept today that replaces our current code with code that uses libunwind. It works nicely on the i686 desktop and so went ahead and compiled that code on the ARM platform that we are using. Unfortunately without much success. I can access the instruction pointer and resolve the name of the current procedure. Unfortunately stepping up the stack doesn't seem to work on the ARM. unw_step() returns 0 on the first call. This was with the 0.99 release. I have then tried the same with a current git checkout. Unfortunately the results were even worse. With that version I can't even resolve the name of the current procedure any longer. So I'd like to know what the current state of the support for ARM is. Is what I am trying to do supposed to work? Should I be trying a particular branch perhaps? Thanks in advance for your help, Sven -- Sven Neumann <[email protected]> RAUMFELD GmbH _______________________________________________ Libunwind-devel mailing list [email protected] http://lists.nongnu.org/mailman/listinfo/libunwind-devel
