From: blaisorblade_spam@yahoo.it
To: bstroesser@fujitsu-siemens.com
Cc: user-mode-linux-devel@lists.sourceforge.net, blaisorblade_spam@yahoo.it
Subject: [uml-devel] [patch 1/1] uml: add stack content to dumps
Date: Tue, 30 Nov 2004 20:30:46 +0100 [thread overview]
Message-ID: <20041130193047.3370F8D743@zion.localdomain> (raw)
Copy some code from i386 to print the stack content. Rough form yet, should
work although.
Signed-off-by: Paolo 'Blaisorblade' Giarrusso <blaisorblade_spam@yahoo.it>
---
linux-2.6.10-rc-paolo/arch/um/kernel/sysrq.c | 40 +++++++++++++++++++++++----
1 files changed, 35 insertions(+), 5 deletions(-)
diff -puN arch/um/kernel/sysrq.c~uml-add-stack-content-to-dumps arch/um/kernel/sysrq.c
--- linux-2.6.10-rc/arch/um/kernel/sysrq.c~uml-add-stack-content-to-dumps 2004-11-30 18:32:12.000000000 +0100
+++ linux-2.6.10-rc-paolo/arch/um/kernel/sysrq.c 2004-11-30 20:27:06.540447816 +0100
@@ -15,11 +15,13 @@
void show_trace(unsigned long * stack)
{
/* XXX: Copy the CONFIG_FRAME_POINTER stack-walking backtrace from
- * arch/i386/kernel/traps.c. */
+ * arch/i386/kernel/traps.c, and then move this to sys-i386/sysrq.c.*/
unsigned long addr;
- if (!stack)
+ if (!stack) {
stack = (unsigned long*) &stack;
+ WARN_ON(1);
+ }
printk("Call Trace: \n");
while (((long) stack & (THREAD_SIZE-1)) != 0) {
@@ -34,7 +36,8 @@ void show_trace(unsigned long * stack)
}
/*
- * The architecture-independent dump_stack generator
+ * stack dumps generator - this is used by arch-independent code.
+ * And this is identical to i386 currently.
*/
void dump_stack(void)
{
@@ -44,7 +47,34 @@ void dump_stack(void)
}
EXPORT_SYMBOL(dump_stack);
-void show_stack(struct task_struct *task, unsigned long *sp)
+/*Stolen from arch/i386/kernel/traps.c */
+static int kstack_depth_to_print = 24;
+
+/* This recently started being used in arch-independent code too, as in
+ * kernel/sched.c.*/
+void show_stack(struct task_struct *task, unsigned long *esp)
{
- show_trace(sp);
+ unsigned long *stack;
+ int i;
+
+ if (esp == NULL) {
+ if (task != current) {
+ esp = (unsigned long *) KSTK_ESP(task);
+ /* Which one? No actual difference - just coding style.*/
+ //esp = (unsigned long *) PT_REGS_IP(&task->thread.regs);
+ } else {
+ esp = (unsigned long *) &esp;
+ }
+ }
+
+ stack = esp;
+ for(i = 0; i < kstack_depth_to_print; i++) {
+ if (kstack_end(stack))
+ break;
+ if (i && ((i % 8) == 0))
+ printk("\n ");
+ printk("%08lx ", *stack++);
+ }
+
+ show_trace(esp);
}
_
-------------------------------------------------------
SF email is sponsored by - The IT Product Guide
Read honest & candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now.
http://productguide.itmanagersjournal.com/
_______________________________________________
User-mode-linux-devel mailing list
User-mode-linux-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/user-mode-linux-devel
next reply other threads:[~2004-11-30 19:27 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-11-30 19:30 blaisorblade_spam [this message]
2004-12-02 3:57 ` [uml-devel] Kernel panic: Kernel stack overflow Peter
2004-12-02 20:19 ` Jeff Dike
2004-12-04 6:13 ` Peter
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=20041130193047.3370F8D743@zion.localdomain \
--to=blaisorblade_spam@yahoo.it \
--cc=bstroesser@fujitsu-siemens.com \
--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