From 2746a1d4b578bf10cacbfa3ada1f03131cd9e2d4 Mon Sep 17 00:00:00 2001
From: Laura Abbott <lauraa@codeaurora.org>
Date: Tue, 15 Apr 2014 19:09:09 -0700
Subject: [PATCH] linux-ramdump-parser-v2: Add extra newline before printing
stack
It's bothersome at a fundamental level that the first line of the
stack trace is printed out on the same line as the 'Stack:' tag.
Fix it.
Change-Id: I895ad0969c4afb5b081ad10dca180a2bb1178291
---
linux-ramdump-parser-v2/parsers/taskdump.py | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/linux-ramdump-parser-v2/parsers/taskdump.py b/linux-ramdump-parser-v2/parsers/taskdump.py
index f00232c..ad1ca27 100644
--- a/linux-ramdump-parser-v2/parsers/taskdump.py
+++ b/linux-ramdump-parser-v2/parsers/taskdump.py
@@ -81,7 +81,7 @@ def dump_thread_group(ramdump, thread_group, task_out, check_for_panic=0):
first = 1
task_out.write(' Task name: {0} pid: {1} cpu: {2}\n state: 0x{3:x} exit_state: 0x{4:x} stack base: 0x{5:x}\n'.format(
thread_task_name, thread_task_pid, ramdump.read_int(threadinfo + offset_cpu), task_state, task_exit_state, addr_stack))
- task_out.write(' Stack:')
+ task_out.write(' Stack:\n')
ramdump.unwind.unwind_backtrace(
ramdump.thread_saved_sp(next_thread_start),
ramdump.thread_saved_fp(next_thread_start),
--
GitLab