Date: Thu, 29 Aug 1996 07:49:43 -0700 From: Paul Traina <pst@shockwave.com> To: Julian Elischer <julian@whistle.com> Cc: hackers@FreeBSD.org Subject: Re: gdb remote Message-ID: <199608291449.HAA02910@precipice.shockwave.com> In-Reply-To: Your message of "Thu, 29 Aug 1996 06:48:45 PDT." <32259FBD.41C67EA6@whistle.com>
next in thread | previous in thread | raw e-mail | index | archive | help
I don't know why yours is hellishly slow, it sounds like the tty code is not syncing properly or you're getting lots of retries. In addition, all the breakpoints and continues and steps work fine for me. From: Julian Elischer <julian@whistle.com> Subject: Re: gdb remote Julian Elischer wrote: > > Ok I think I have it all set up.. > but I get > A ok I have got a bit further.. booting -g I can get the kernel to fall into the appropriate debugger by hitting ctl-alt-esc on the keyboard. if I have just done a "target remote /dev/cuaa1" then gdb can "kinda" make a connection.. it's hellishly slow..... for example.. the folloing took 1 minute to print out.... (kgdb) bt #0 0xf01adf7d in Debugger () #1 0xf01caf31 in sgetc () #2 0xf01c6737 in pcvt_timeout () #3 0xf01092a4 in softclock () which seems slow to me... but at least you see that much.. you can't DO anything though.. even 'cont' doesn't work... I must be doing something wrong.. Waht does a good config look like? and a good .gdbinit file?
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?199608291449.HAA02910>