From owner-freebsd-hackers Fri Sep 1 11:18:30 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from wally.eecs.harvard.edu (wally.eecs.harvard.edu [140.247.60.30]) by hub.freebsd.org (Postfix) with ESMTP id 94BC037B424 for ; Fri, 1 Sep 2000 11:18:26 -0700 (PDT) Received: from localhost (stein@localhost) by wally.eecs.harvard.edu (8.10.0/8.10.0) with ESMTP id e81IIPo16519; Fri, 1 Sep 2000 14:18:25 -0400 (EDT) Date: Fri, 1 Sep 2000 14:18:25 -0400 (EDT) From: Christopher Stein X-Sender: stein@wally To: freebsd-hackers@freebsd.org, grog@lemis.com Subject: gdb remote connection Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi, I discovered the source of my problem and solved it. For those interested, here is an explanation: The flags of the serial I/O device to be used for remote debugging needs to be changed in the config file. I plugged a null modem cable across the two ports labeled 1 (the other one labeled 2) on the back of the computer. I assumed that these correspond to serial port 1 as the FreeBSD kernel sees the world (wrong assumption). Therefore, I only changed the permissions of sio0 in the config file. I was able to communicate across the serial line using device /dev/cuaa1 and doing things like echo "hello" > /dev/cuaa1. GDB, however, was unable to establish a remote connection when I did "target remote /dev/cuaa1" in kgdb. I started wondering about why the device has the number "1" and not "0". So I decided to change the permissions of sio1 in addition. It works! So it turns out the FreeBSD maps the physically labelled (i.e. etched in metal) port 2 to sio0 and port 1 to sio1! Sweet. -Chris To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message