Date: Tue, 17 Dec 2002 17:58:35 -0800 (PST) From: Julian Elischer <julian@elischer.org> To: Alfred Perlstein <bright@mu.org> Cc: Nate Lawson <nate@root.org>, Archie Cobbs <archie@dellroad.org>, cvs-committers@FreeBSD.org, cvs-all@FreeBSD.org Subject: Re: cvs commit: src/sys/i386/i386 i386-gdbstub.c Message-ID: <Pine.BSF.4.21.0212171752120.24496-100000@InterJet.elischer.org> In-Reply-To: <20021218001104.GC23663@elvis.mu.org>
next in thread | previous in thread | raw e-mail | index | archive | help
On Tue, 17 Dec 2002, Alfred Perlstein wrote: > So it seems that your patch actually makes gdb a lot safer, while the > sysctl preserves the old weirder behavior that some people have come > to depend on. > > If so, I like it. :) > Ok so here's how I generally use ut: boot. get page fault.. drop into ddb run various tests to see what might be wrong.. (e.g. check krnel trace buffers, ps, backtrace a few processes) if I decide I need more.. I fire up gdb on teh serial link and type gdb\r s\r then I'm in gdb when I finish I expect 'detatch' to put me back where I started (in ddb) so I can check things I forgot, and to type 'panic' so I can take a coredump if needs be.. If this doesn't work for you, how did you get into gdb? boot -g? if you can tell how you got into gdb you can figure out where to return to. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe cvs-all" 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.21.0212171752120.24496-100000>