Nick Hibma writes:
> In general it is well possible to single step anything in the
> kernel. You might find occasions where things stop working, and odd
> cases were things all of a sudden start working, but normally, apart
> from hardware things, most things are not time critical, or create
> pro
> > You can single step at boot time, by setting the flags in the loader.
>
> None of this will be source level, correct? Will it at least have labels if
> i use a debug kernel?
With remote debugging it will be source level debugging, with DDB it
will not. In both cases it will have labels. Eve
On Sun, May 21, 2000 at 12:02:53PM +0100, Nick Hibma wrote:
> You can single step at boot time, by setting the flags in the loader.
None of this will be source level, correct? Will it at least have labels if
i use a debug kernel?
jm
--
-
In general it is well possible to single step anything in the
kernel. You might find occasions where things stop working, and odd
cases were things all of a sudden start working, but normally, apart
from hardware things, most things are not time critical, or create
problems through spin locks.
Y
I've used softice for debugging under windows, and i was wondering if gdb
offers similar capabilities. It seems the best way to debug the ECP
parallel port problem is to step through the code during the boot phase.
Can this be done, or is there too much timing-critical stuff going on then?
jm
--
5 matches
Mail list logo
