On Sat, Oct 4, 2014 at 7:09 AM, <[email protected]> wrote: > Did you guys need more details or can commit the patch. Thanks
Yes. Some more context on your use case would help. I suppose you want people to be able to write exception handlers that modify the scratch registers and then resume. In that case you should only be touching code paths guarded by (c->sigcontext_format != AARCH64_SCF_NONE). But the patch seems to touch the normal (call/return) path as well. Why? -Arun _______________________________________________ Libunwind-devel mailing list [email protected] https://lists.nongnu.org/mailman/listinfo/libunwind-devel
