| commit | 1650743cdc0db73478f72c57544ce79ea8f3dda6 | |
| author | Vegard Nossum <vegard.nossum@gmail.com> | |
| Fri, 22 Feb 2008 18:23:58 +0000 (22 19:23 +0100) | ||
| committer | Ingo Molnar <mingo@elte.hu> | |
| Tue, 26 Feb 2008 11:55:58 +0000 (26 12:55 +0100) | ||
| tree | 14d6218acfc06a20450cf80365a1854af4c096b0 | treesnapshot (tar.gz zip) |
| parent | ed2b7e2b1d1ae201afe8fbd111632074b7b53ed4 | commitdiff |
x86: don't save unreliable stack trace entries
Currently, there is no way for print_stack_trace() to determine whether
a given stack trace entry was deemed reliable or not, simply because
save_stack_trace() does not record this information. (Perhaps needless
to say, this makes the saved stack traces A LOT harder to read, and
probably with no other benefits, since debugging features that use
save_stack_trace() most likely also require frame pointers, etc.)
This patch reverts to the old behaviour of only recording the reliable trace
entries for saved stack traces.
Signed-off-by: Vegard Nossum <vegardno@ifi.uio.no>
Acked-by: Arjan van de Ven <arjan@linux.intel.com>
Signed-off-by: Ingo Molnar <mingo@elte.hu>
Currently, there is no way for print_stack_trace() to determine whether
a given stack trace entry was deemed reliable or not, simply because
save_stack_trace() does not record this information. (Perhaps needless
to say, this makes the saved stack traces A LOT harder to read, and
probably with no other benefits, since debugging features that use
save_stack_trace() most likely also require frame pointers, etc.)
This patch reverts to the old behaviour of only recording the reliable trace
entries for saved stack traces.
Signed-off-by: Vegard Nossum <vegardno@ifi.uio.no>
Acked-by: Arjan van de Ven <arjan@linux.intel.com>
Signed-off-by: Ingo Molnar <mingo@elte.hu>
| arch/x86/kernel/stacktrace.c | diffblobblamehistory |