Hi, > It looks like you are for some reason landing to one byte before the actual > function. Subtracting one from the caller address is indeed the default logic > when walking up the call tree: you have to back off into the call instruction > itself, the function might end with the call, so it's valid to look at the > byte after the call.
Argh - not valid to look at the byte after the call. Regards, Lassi _______________________________________________ Libunwind-devel mailing list [email protected] http://lists.nongnu.org/mailman/listinfo/libunwind-devel
