From owner-freebsd-current Tue May 6 16:19:30 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id QAA12648 for current-outgoing; Tue, 6 May 1997 16:19:30 -0700 (PDT) Received: from pluto.plutotech.com (root@pluto100.plutotech.com [206.168.67.137]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id QAA12642 for ; Tue, 6 May 1997 16:19:27 -0700 (PDT) Received: from narnia.plutotech.com (narnia.plutotech.com [206.168.67.130]) by pluto.plutotech.com (8.8.5/8.8.3) with ESMTP id RAA12200 for ; Tue, 6 May 1997 17:19:27 -0600 (MDT) Message-Id: <199705062319.RAA12200@pluto.plutotech.com> X-Mailer: exmh version 2.0beta 12/23/96 To: current@FreeBSD.org Subject: Problems using remote gdb Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Tue, 06 May 1997 18:18:05 -0600 From: "Justin T. Gibbs" Sender: owner-current@FreeBSD.org X-Loop: FreeBSD.org Precedence: bulk Anyone have any advice on remote kernel debugging. It used to work for me, but now I just get: (kgdb) target remote /dev/cuaa0 Remote debugging using /dev/cuaa0 Ignoring packet error, continuing... Ignoring packet error, continuing... Couldn't establish connection to remote target I've verified that the null modem cable I have is working by using tip on both sides. From the debugging output, it seems that the remote side is simply not responding at all: (kgdb) set remotedebug 1 (kgdb) target remote /dev/cuaa0 Remote debugging using /dev/cuaa0 Sending packet: $Hc-1#09...Sending packet: $Hc-1#09...Sending packet: $Hc-1#09...Sending packet: $Hc-1#09...Timed out. Timed out. Timed out. Ignoring packet error, continuing... Sending packet: $qOffsets#4b...Sending packet: $qOffsets#4b...Sending packet: $qOffsets#4b...Sending packet: $qOffsets#4b...Timed out. Timed out. Timed out. Ignoring packet error, continuing... __ Justin T. Gibbs =========================================== FreeBSD - Turning PCs into workstations ===========================================