From: blaisorblade_spam@yahoo.it
To: akpm@osdl.org
Cc: linux-kernel@vger.kernel.org, jdike@addtoit.com,
user-mode-linux-devel@lists.sourceforge.net,
blaisorblade_spam@yahoo.it, bstroesser@fujitsu-siemens.com
Subject: [uml-devel] [patch 10/11] uml: add stack addresses to dumps
Date: Thu, 13 Jan 2005 22:01:11 +0100 [thread overview]
Message-ID: <20050113210111.86DE01FEFB@zion> (raw)
From: Bodo Stroesser <bstroesser@fujitsu-siemens.com>
Add stack addresses to print of symbols from stack trace.
For stack analysis it's important to have this information.
Signed-off-by: Bodo Stroesser <bstroesser@fujitsu-siemens.com>
For UML, we should also copy the CONFIG_FRAME_POINTER stack walking from i386,
and move the result to sys-i386.
Another note: this should be done for i386 also, if ksymoops does not have
problems.
Signed-off-by: Paolo 'Blaisorblade' Giarrusso <blaisorblade_spam@yahoo.it>
---
linux-2.6.11-paolo/arch/um/kernel/sysrq.c | 5 +++--
1 files changed, 3 insertions(+), 2 deletions(-)
diff -puN arch/um/kernel/sysrq.c~uml-add-stack-addresses-to-dumps arch/um/kernel/sysrq.c
--- linux-2.6.11/arch/um/kernel/sysrq.c~uml-add-stack-addresses-to-dumps 2005-01-13 21:54:57.450269544 +0100
+++ linux-2.6.11-paolo/arch/um/kernel/sysrq.c 2005-01-13 21:56:09.250354272 +0100
@@ -25,12 +25,13 @@ void show_trace(unsigned long * stack)
printk("Call Trace: \n");
while (((long) stack & (THREAD_SIZE-1)) != 0) {
- addr = *stack++;
+ addr = *stack;
if (__kernel_text_address(addr)) {
- printk(" [<%08lx>]", addr);
+ printk("%08lx: [<%08lx>]", (unsigned long) stack, addr);
print_symbol(" %s", addr);
printk("\n");
}
+ stack++;
}
printk("\n");
}
_
-------------------------------------------------------
The SF.Net email is sponsored by: Beat the post-holiday blues
Get a FREE limited edition SourceForge.net t-shirt from ThinkGeek.
It's fun and FREE -- well, almost....http://www.thinkgeek.com/sfshirt
_______________________________________________
User-mode-linux-devel mailing list
User-mode-linux-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/user-mode-linux-devel
reply other threads:[~2005-01-13 21:58 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20050113210111.86DE01FEFB@zion \
--to=blaisorblade_spam@yahoo.it \
--cc=akpm@osdl.org \
--cc=bstroesser@fujitsu-siemens.com \
--cc=jdike@addtoit.com \
--cc=linux-kernel@vger.kernel.org \
--cc=user-mode-linux-devel@lists.sourceforge.net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox