From: Jan Hudec <bulb@ucw.cz>
To: Pat LaVarre <p.lavarre@ieee.org>
Cc: linux-fsdevel@vger.kernel.org
Subject: Re: fs oops debuggable in 2.6 with one one machine
Date: Thu, 23 Oct 2003 14:49:39 +0200 [thread overview]
Message-ID: <20031023124939.GC1465@vagabond> (raw)
In-Reply-To: <1066826696.7159.70.camel@patehci2>
On Wed, Oct 22, 2003 at 06:44:56 -0600, Pat LaVarre wrote:
> Anybody yet work out in detail how to debug oops in filesystems without
> connecting a second machine?
Yes, you can use the user-mode linux. Project homepage is
user-mode-linux.sourceforge.net.
All code of user-mode linux except arch specific parts is the same as on
normal kernel, so chances are high, that this will be reproducible.
It is fully debuggable with gdb. However, gdb does not seem to
understand output from gcc-3 correctly, so gcc-2.95 (or using -gstabs
option to gcc) is needed.
-------------------------------------------------------------------------------
Jan 'Bulb' Hudec <bulb@ucw.cz>
prev parent reply other threads:[~2003-10-23 12:49 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-10-22 12:44 fs oops debuggable in 2.6 with one one machine Pat LaVarre
2003-10-23 12:49 ` Jan Hudec [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=20031023124939.GC1465@vagabond \
--to=bulb@ucw.cz \
--cc=linux-fsdevel@vger.kernel.org \
--cc=p.lavarre@ieee.org \
/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