From: allan.graves@oracle.com
To: user-mode-linux-devel@lists.sourceforge.net
Subject: [uml-devel] Best way to debug?
Date: Thu, 21 Jul 2005 14:59:49 +0000 (GMT) [thread overview]
Message-ID: <21786771.1121957989655.JavaMail.oracle@web265.oracle.com> (raw)
This is a question to you kernel developers... when using UML, what's teh best way to debug a kernel panic? Get UML to generate a core? Setup netdump or some such? How do you guys usually do it?
Allan
-------------------------------------------------------
SF.Net email is sponsored by: Discover Easy Linux Migration Strategies
from IBM. Find simple to follow Roadmaps, straightforward articles,
informative Webcasts and more! Get everything you need to get up to
speed, fast. http://ads.osdn.com/?ad_id=7477&alloc_id=16492&op=click
_______________________________________________
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:[~2005-07-21 15:00 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-07-21 14:59 allan.graves [this message]
2005-07-21 15:38 ` [uml-devel] Best way to debug? Jeff Dike
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=21786771.1121957989655.JavaMail.oracle@web265.oracle.com \
--to=allan.graves@oracle.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.