* How to debug an oops?
@ 2001-03-30 0:47 Tony Hoyle
2001-03-30 1:33 ` Tony Hoyle
0 siblings, 1 reply; 2+ messages in thread
From: Tony Hoyle @ 2001-03-30 0:47 UTC (permalink / raw)
To: linux-kernel
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
^ permalink raw reply [flat|nested] 2+ messages in thread
* Re: How to debug an oops?
2001-03-30 0:47 How to debug an oops? Tony Hoyle
@ 2001-03-30 1:33 ` Tony Hoyle
0 siblings, 0 replies; 2+ messages in thread
From: Tony Hoyle @ 2001-03-30 1:33 UTC (permalink / raw)
To: Tony Hoyle; +Cc: linux-kernel
Sorry, came across a bit strong on that message. It's 2am and I'm tired.
Stupid thing is I fixed the bug...
Tony
--
Don't click on this sig - a cyberwoozle will eat your underwear.
tmh@magenta-netlogic.com http://www.nothing-on.tv
^ permalink raw reply [flat|nested] 2+ messages in thread
end of thread, other threads:[~2001-03-30 1:34 UTC | newest]
Thread overview: 2+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2001-03-30 0:47 How to debug an oops? Tony Hoyle
2001-03-30 1:33 ` Tony Hoyle
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®