summaryrefslogtreecommitdiffstats
path: root/scripts/genksyms
diff options
context:
space:
mode:
authorIngo Molnar <mingo@elte.hu>2008-02-14 09:07:01 +0100
committerThomas Gleixner <tglx@linutronix.de>2008-05-26 16:15:32 +0200
commit5cb273013e182a35e7db614d3e20a144cba71e53 (patch)
treef027f389e3d9d2ab9750fdc81399f6c5df385fb2 /scripts/genksyms
parent517a92c4e19fcea815332d3155e9fb7723251274 (diff)
downloadlinux-stable-5cb273013e182a35e7db614d3e20a144cba71e53.tar.gz
linux-stable-5cb273013e182a35e7db614d3e20a144cba71e53.tar.bz2
linux-stable-5cb273013e182a35e7db614d3e20a144cba71e53.zip
panic: print out stacktrace if DEBUG_BUGVERBOSE
if CONFIG_DEBUG_BUGVERBOSE is set then the user most definitely wanted to see as much information about kernel crashes as possible - so give them at least a stack dump. this is particularly useful for stackprotector related panics, where the stacktrace can give us the exact location of the (attempted) attack. Pointed out by pageexec@freemail.hu in the stackprotector breakage threads. Signed-off-by: Ingo Molnar <mingo@elte.hu> Signed-off-by: Thomas Gleixner <tglx@linutronix.de>
Diffstat (limited to 'scripts/genksyms')
0 files changed, 0 insertions, 0 deletions