From: Tony Hoyle <tmh@magenta-netlogic.com>
To: linux-kernel@vger.kernel.org
Subject: How to debug an oops?
Date: Fri, 30 Mar 2001 01:47:25 +0100 [thread overview]
Message-ID: <3AC3D79D.7000503@magenta-netlogic.com> (raw)
Nobody seems interested in the spinlock bugs in usb so I'm trying to
track it down myself. I have a copy of an oops (posted earlier) but it
doesn't give the line number of the error, so it's impossible to find
out where it's failing.
Will kdb be any help? Is it a source debugger or just a glorified hex
editor? I need to be able to break into the kernel and single step
through the calls to work out what is going on.
I'm really out of my depth trying to debug this, but I hate having to
boot a UP kernel just to use usb.
Tony
--
Don't click on this sig - a cyberwoozle will eat your underwear.
tmh@magenta-netlogic.com http://www.nothing-on.tv
next reply other threads:[~2001-03-30 0:48 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-03-30 0:47 Tony Hoyle [this message]
2001-03-30 1:33 ` Tony Hoyle
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=3AC3D79D.7000503@magenta-netlogic.com \
--to=tmh@magenta-netlogic.com \
--cc=linux-kernel@vger.kernel.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
all inboxes | Powered by JetHome®