Date: Sun, 21 May 2000 12:02:53 +0100 (BST) From: Nick Hibma <n_hibma@calcaphon.com> To: J McKitrick <jcm@freebsd-uk.eu.org> Cc: hackers@freebsd.org Subject: Re: boot/kernel debugging Message-ID: <Pine.BSF.4.20.0005211157520.797-100000@localhost> In-Reply-To: <20000518045219.A59839@dogma.freebsd-uk.eu.org>
next in thread | previous in thread | raw e-mail | index | archive | help
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. You can single step at boot time, by setting the flags in the loader. set boot_ddb # jump to debugger set boot_gdb # use remote gdb for debugging by default Hope this helps. Nick > 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 > -- > ------------------------------------------------------------------- > Jonathon McKitrick -- jcm@freebsd-uk.eu.org > I am a bomb technician. If you see me running, try to keep up. > ------------------------------------------------------------------- > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-hackers" in the body of the message > -- n_hibma@webweaving.org n_hibma@freebsd.org USB project http://www.etla.net/~n_hibma/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?Pine.BSF.4.20.0005211157520.797-100000>