trace: strip leading unimportant frames from backtrace
First couple of frames always come from trace logging functions. I think we should not show them because they do not add any information. There was already a list of function names which should be filtered out. This is not appropriate in this case because tracing goes through a function named 'log' which is a pretty generic name and could as well be an application symbol, so we cannot just filter out all functions named 'log. This patch adds support for knocking off a leading sequence of frames form the backtrace which is more accurate and seems good enough. Reviewed-by:Nadav Har'El <nyh@cloudius-systems.com> Signed-off-by:
Tomasz Grabiec <tgrabiec@cloudius-systems.com> Signed-off-by:
Pekka Enberg <penberg@cloudius-systems.com>
Please register or sign in to comment