On 17/06/2019 09:12, Jan Beulich wrote: > Nothing (afaics) guarantees that the original frame's stack pointer
I'd drop the (afaics), because the answer really is nothing. > points at readable memory. Avoid a (likely nested) crash by attaching > exception recovery to the read (making it a single read at the same > time). Don't even invoke _show_trace() in case of a non-readable top > slot. > > Signed-off-by: Jan Beulich <jbeul...@suse.com> Reviewed-by: Andrew Cooper <andrew.coop...@citrix.com> _______________________________________________ Xen-devel mailing list Xen-devel@lists.xenproject.org https://lists.xenproject.org/mailman/listinfo/xen-devel
