From owner-freebsd-questions@FreeBSD.ORG Wed Jun 23 00:53:01 2004 Return-Path: Delivered-To: freebsd-questions@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id A4D6516A4CE for ; Wed, 23 Jun 2004 00:53:01 +0000 (GMT) Received: from mail.teel.ws (teel.ws [209.151.109.182]) by mx1.FreeBSD.org (Postfix) with SMTP id CA27B43D48 for ; Wed, 23 Jun 2004 00:52:59 +0000 (GMT) (envelope-from mark@teel.ws) Received: (qmail 24324 invoked by uid 513); 23 Jun 2004 00:52:58 -0000 Received: from mark@teel.ws by dmz1 by uid 508 with qmail-scanner-1.22-st-qms Clear:RC:0(192.168.0.110):SA:0(0.0/4.0):. Processed in 0.603928 secs); 23 Jun 2004 00:52:58 -0000 X-Spam-Status: No, hits=0.0 required=4.0 X-Antivirus-MYDOMAIN-Mail-From: mark@teel.ws via dmz1 X-Antivirus-MYDOMAIN: 1.22-st-qms (Clear:RC:0(192.168.0.110):SA:0(0.0/4.0):. Processed in 0.603928 secs Process 24315) Received: from unknown (HELO teel.ws) (mark@teel.ws@192.168.0.110) by mail.teel.ws with SMTP; 23 Jun 2004 00:52:58 -0000 Message-ID: <40D8D464.2080407@teel.ws> Date: Tue, 22 Jun 2004 19:52:52 -0500 From: Mark Teel User-Agent: Mozilla Thunderbird 0.5 (Windows/20040207) X-Accept-Language: en-us, en MIME-Version: 1.0 To: freebsd-questions@freebsd.org Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Subject: Problem with Remote 5.2.1 Kernel Debugging X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 23 Jun 2004 00:53:01 -0000 Hello: I have configured remote kernel debugging as prescribed in the developer's handbook. I am able to remotely connect to the target and step through code, but once I enter "cont" in gdb on the debug machine, I cannot ever "interrupt" or "break" the target kernel execution. It is as if the Ctrl-C character is being ignored on the target. The target kernel was built with the ddb and -g options set, using config -g. Has anyone seen such a problem? This is the last hurdle before I can start debugging my wireless device driver. Any advice would be appreciated. Thanks in advance, Mark