On 11/01/2015 05:00 PM, Jungseok Lee wrote:
On Oct 30, 2015, at 2:25 PM, AKASHI Takahiro wrote:
Hi Akashi,
Function graph tracer modifies a return address (LR) in a stack frame
to hook a function return. This will result in many useless entries
(return_to_handler) showing up in a stack
On 11/01/2015 05:00 PM, Jungseok Lee wrote:
On Oct 30, 2015, at 2:25 PM, AKASHI Takahiro wrote:
Hi Akashi,
Function graph tracer modifies a return address (LR) in a stack frame
to hook a function return. This will result in many useless entries
(return_to_handler) showing up in a stack
On Oct 30, 2015, at 2:25 PM, AKASHI Takahiro wrote:
Hi Akashi,
> Function graph tracer modifies a return address (LR) in a stack frame
> to hook a function return. This will result in many useless entries
> (return_to_handler) showing up in a stack tracer's output.
>
> This patch replaces such
On Oct 30, 2015, at 2:25 PM, AKASHI Takahiro wrote:
Hi Akashi,
> Function graph tracer modifies a return address (LR) in a stack frame
> to hook a function return. This will result in many useless entries
> (return_to_handler) showing up in a stack tracer's output.
>
> This patch replaces such
Function graph tracer modifies a return address (LR) in a stack frame
to hook a function return. This will result in many useless entries
(return_to_handler) showing up in a stack tracer's output.
This patch replaces such entries with originals values preserved in
current->ret_stack[].
Function graph tracer modifies a return address (LR) in a stack frame
to hook a function return. This will result in many useless entries
(return_to_handler) showing up in a stack tracer's output.
This patch replaces such entries with originals values preserved in
current->ret_stack[].
6 matches
Mail list logo
