On Tue, Sep 6, 2011 at 11:33 AM, Shan Shan <[email protected]> wrote:
> It works fine and even unwinds stack properly :-). This unit test app was > crashing before even when i just link with -lunwind. Is this something > specific to "-funwind-tables" option? Do all app needs to be compiled with > this option? or may be out of the 4 options tried by libunwind (arm) only > this option is stable? If you want to get a backtrace at *any* instruction in the program, yes you should use -funwind-tables. Otherwise, gcc generates enough information only from call/return sites. Usually, the challenge is to make sure that everything linked to your target binary is compiled with the desired options. -Arun _______________________________________________ Libunwind-devel mailing list [email protected] https://lists.nongnu.org/mailman/listinfo/libunwind-devel
