Date: Tue, 30 Sep 2003 09:32:54 -0700 From: Sam Leffler <sam@errno.com> To: Bruce Evans <bde@zeta.org.au>, "Greg 'groggy' Lehey" <grog@freebsd.org> Cc: FreeBSD current users <FreeBSD-current@freebsd.org> Subject: Re: Serial debug broken in recent -CURRENT? Message-ID: <200309300932.54682.sam@errno.com> In-Reply-To: <20030930204919.A4354@gamplex.bde.org> References: <20030929083007.GA33083@wantadilla.lemis.com> <20030930074500.GY45668@wantadilla.lemis.com> <20030930204919.A4354@gamplex.bde.org>
next in thread | previous in thread | raw e-mail | index | archive | help
On Tuesday 30 September 2003 04:01 am, Bruce Evans wrote: > On Tue, 30 Sep 2003, Greg 'groggy' Lehey wrote: > > On Tuesday, 30 September 2003 at 16:23:35 +1000, Bruce Evans wrote: > > > On Mon, 29 Sep 2003, Greg 'groggy' Lehey wrote: > > >> After building a new kernel, remote serial gdb no longer works. When > > >> I issue a 'continue' command, I lose control of the system, but it > > >> doesn't continue running. Has anybody else seen this? > > > > > > It works as well as it did a few months ago here. (Not very well > > > compared with ddb. E.g., calling a function is usually fatal.) > > > > Hmm, that's not what Sam or I are seeing. How old is your kernel? > > You *are* able to continue, right? Everything else works for me. > > I didn't test with my kernel; I tested with almost-current SMP and !SMP > kernels (amost-current = 217 lines of patches; my kernel = 96934 lines > of patches). They were about half an hour old when I tried it. I tested > little more than continuing from Debugger(). I didn't test using optional > foot shooting devices like acpi or modules. It reliably locks up for me when you break into a running system; set a breakpoint; and then continue. Machine is UP+HTT. Haven't tried other machines. Sam
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?200309300932.54682.sam>