Date: Fri, 1 Sep 2000 13:22:05 -0400 (EDT) From: Christopher Stein <stein@eecs.harvard.edu> To: Greg Lehey <grog@lemis.com> Cc: freebsd-hackers@FreeBSD.ORG Subject: Re: remote gdb debugging Message-ID: <Pine.OSF.4.20.0009011053110.18467-100000@wally> In-Reply-To: <20000829120352.K11422@wantadilla.lemis.com>
next in thread | previous in thread | raw e-mail | index | archive | help
/dev/cuaa1 turned out to be the culprit. I tested this by `echo "hello" > /dev/cuaa1` on the debugger and `cat /dev/cuaa1` on the debuggee. The hello makes it across. Now I'm having some "packet error" problems with kgdb. On the debuggee I ctrl-alt-esc into ddb and do: db> gdb db> step <waits for remote connection > From the debugger I do: (gdb) target remote /dev/cuaa1 Remote debugging using /dev/cuaa1 Ignoring packet error, continuing... Ignoring packet error, continuing... Ignoring packet error, continuing... Couldn't establish connection to remote target Malformed response to offset query, timeout (gdb) Anyone seen this before? What did I miss? These two systems are identical hardware-wise .. so I would expect the baud rates to match (unless gdb does some setting in the background). thanks -Chris > > > > hhmmm.. any suggestions? /dev/ttyd1 worked for a 3.3/4.0-pre install in > > the past, but doesn't work for this new system, which is quite similar. > > Nothing has changed between 4.0 and now. I've had the devil's own job > in the past, and I suspect you've hit a different problem. Do you > have a breakout box on the line? If so, what's it showing? Also, > you've set the sio flags correctly (0x80 or 0x90) on the debugged > machine, right? > > Greg > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?Pine.OSF.4.20.0009011053110.18467-100000>