Hi, On Mon, 2010-08-02 at 14:29 +0300, Lassi Tuura wrote:
> > I've tried that now, unfortunately without much success. Here's the > > output from a simple test application with debug output enabled. As you > > can see, dwarf_step() fails and then the code crashes in the alternative > > approach using the frame chain: > > I submitted a stack of patches related to this for x86_64 a little > while ago. Your problem can be something else but it looks related. > Can you check in GDB or some other way where the address 0x400406b7 > resides? > > If it is related to my validation patches, I suggest you check you use > GCC which generates correct frame info in the first place (4.5.0 or > newer) for as much code as you can, then check to make sure addresses > are validated correctly on your platform. We are still using gcc 4.3 and while it would be relatively straight-forward to update to 4.4, I don't think there's support for version 4.5 in buildroot yet. Would updating to gcc 4.4 be worthwhile? Regards, Sven _______________________________________________ Libunwind-devel mailing list [email protected] http://lists.nongnu.org/mailman/listinfo/libunwind-devel
