On Mon, 3 Apr 2000, Scott Foehner wrote:
> Most of that info was probably not useful to you, though, since it looks like
> you need to be working with 2.2.14. I don't really have plans to advance a
> 2.2.x series of the patch, but if you were to send me one with the fixes/
> additions you noted, I could put it up on the web site.
Well, 2.2.X. Right now X is 14 due to RH6.2...
> I don't quite understand why you want to be able to drop into the debugger
> when doing a sysrq on the machine you are debugging. If you just send the
Cause I sometimes want to be able to reboot the slave machine without
intervention (ie, power outage) and then decide that I will be debugging
this session w/o rebooting it.
> break character from the machine running gdb, it will drop into the debugger.
> I think this is the preferred way, because that way you don't have to mess
> with the machine running the kernel you are debugging.
Oh, I'm doing kernel-modules, not kernel hacking. I don't care what
kernel the machine is running... And I want to attach the debugger after
boot, not break. Basically I was just trying to replace the "gdbstub"
program that no longer comes with the patch.
> I'm not sure why you are seeing the oops. Are you using kdb as well? If you
> add kdb, you might be able to debug the problem. If you have more details on
> why the kernel is panicing, let me know.
I don't think so, unless RH6.2 includes it. I just dropped the patch into
a stock 6.2 /usr/src/linux tree, and compilied.
I tried again with rc5des running, and it didn't crash... Now I'm really
confused. I don't yet know if it will work well enough for my needs as
is, but making sure that something other than the idle task is running
seems to have fixed the immediate crash.
I'll look into what patches RH6.2 comes with...
Doug
--
dougk@xxxxxxxxxxx
dkilpatr@xxxxxxx
|