Date: Fri, 18 Jun 1999 17:37:36 -0500 (CDT) From: Jonathan Lemon <jlemon@americantv.com> To: grog@lemis.com, current@freebsd.org Subject: Re: Remote serial gdb--status? Message-ID: <199906182237.RAA23654@free.pcs> In-Reply-To: <local.mail.freebsd-current/19990618114450.Q9893@freebie.lemis.com>
next in thread | previous in thread | raw e-mail | index | archive | help
In article <local.mail.freebsd-current/19990618114450.Q9893@freebie.lemis.com> you write: >I've been away from work for several weeks, and I now find that I can >no longer start remote serial gdb. I am using sio0 on the debugged >machine side, and sio1 on the debugging machine side. Here are the >relevant dmesg outputs: > >panic (debugged machine): > >sio0: system console >sio0: gdb debugging port >... >sio0 at port 0x3f8-0x3ff irq 4 flags 0x90 on isa0 >sio0: type 16550A > >freebie (debugging machine): > >sio1 at port 0x2f8-0x2ff irq 3 on isa0 >sio1: type 16550A >sio1: interrupting at irq 3 > >I can communicate fine using cu, and a breakout box shows all modem >signals asserte (DCD, DTR, DSR, RTS, CTS). When I go into remote >debug on panic, RxD flashes, and when freebie tries to attach to >panic, TxD flashes, so I'm obviously addressing the correct ports. >I've checked the bit rate and configuration of the ports before going >into debug, and they look right (9600 bps, cs8, -istrip, -parenb). I >don't know what else to look for. Any ideas? How about ``options GDB_REMOTE_CHAT'' in the kernel? I was just running gdb over a serial line today (flags 0x80), and didn't have any problems. -- Jonathan To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?199906182237.RAA23654>