From: Jeff Dike <jdike@addtoit.com>
To: Torsten Boob <ddflatrate@web.de>
Cc: user-mode-linux-devel@lists.sourceforge.net
Subject: Re: [uml-devel] Kernel Panic
Date: Tue, 28 Oct 2003 20:15:03 -0500 [thread overview]
Message-ID: <200310290115.h9T1F3LJ003833@ccure.karaya.com> (raw)
In-Reply-To: Your message of "Tue, 28 Oct 2003 23:02:44 +0100." <20031028230244.0382a7e2.ddflatrate@web.de>
ddflatrate@web.de said:
> Kernel panic: Kernel mode fault at addr 0x28, ip 0xa003d050
Well, 'i sym *0xa003d050' will tell you where the segfault happened, at
least.
> And then the whole UML goes down. No chance to make a backtrace,
> because gdb is killed too.
Hummm, that seems bad. Any more info on that?
One thing I do when gdb isn't useful, and I know where I want to stop, is
put a 'printk("something\n"); while(1) ;' there, and just run UML with no
debugger.
When it stops:
if you're using skas mode, just attach gdb to it
if you're using tt mode, do the following
kill -STOP the 'R' UML process
kill -9 the tracing thread
attach gdb to the -STOPped process
Either way, you've got your stack trace.
Jeff
-------------------------------------------------------
This SF.net email is sponsored by: SF.net Giveback Program.
Does SourceForge.net help you be more productive? Does it
help you create better code? SHARE THE LOVE, and help us help
YOU! Click Here: http://sourceforge.net/donate/
_______________________________________________
User-mode-linux-devel mailing list
User-mode-linux-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/user-mode-linux-devel
prev parent reply other threads:[~2003-10-29 1:15 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-10-28 22:02 [uml-devel] Kernel Panic Torsten Boob
2003-10-29 1:15 ` Jeff Dike [this message]
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=200310290115.h9T1F3LJ003833@ccure.karaya.com \
--to=jdike@addtoit.com \
--cc=ddflatrate@web.de \
--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