Date: Thu, 24 Apr 1997 09:51:23 -0400 From: Bakul Shah <bakul@torrentnet.com> To: Pavlin Ivanov Radoslavov <pavlin@catarina.usc.edu> Cc: hackers@freebsd.org Subject: Re: Kernel remote debugging using gdb Message-ID: <199704241351.JAA13535@chai.plexuscom.com> In-Reply-To: Your message of "Thu, 24 Apr 1997 01:40:52 PDT." <199704240840.BAA06706@catarina.usc.edu>
next in thread | previous in thread | raw e-mail | index | archive | help
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. I haven't yet tried Bruce's latest sio changes so don't know how well they solve the problem.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?199704241351.JAA13535>