Date: Thu, 24 Apr 1997 16:51:53 -0500 From: Jonathan Lemon <jlemon@americantv.com> To: Bakul Shah <bakul@torrentnet.com> Cc: Pavlin Ivanov Radoslavov <pavlin@catarina.usc.edu>, hackers@freebsd.org Subject: Re: Kernel remote debugging using gdb Message-ID: <19970424165153.38383@right.PCS> In-Reply-To: <199704241351.JAA13535@chai.plexuscom.com>; from Bakul Shah on Apr 04, 1997 at 09:51:23AM -0400 References: <199704240840.BAA06706@catarina.usc.edu> <199704241351.JAA13535@chai.plexuscom.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On Apr 04, 1997 at 09:51:23AM -0400, Bakul Shah wrote: > If you can _live_ with sharing the same sio port for console and > gdb, there is a way. Not pretty but it works. First, as Amancio > suggested, swap your connections to the UUG (Unix under GDB :-) so > that the PC is now attached to COM1. Now you can switch between gdb > and a comm program like kermit. The kermit window will show you > all your printfs. Any time you want to drop into gdb, send a break, > stop kermit and switch to gdb and hit ^C in it. If you are in > kermit when the kernel stops due to a breakpoint it is easy to see > and switch to gdb. actually, if you do 'set remotebreak 1' in gdb, then you can use ^C from gdb to drop directly into the debugger. Now, is there any way to get _back_ to DDB after invoking the remote GDB protocol? -- Jonathan
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?19970424165153.38383>