From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 721 invoked by alias); 1 Dec 2002 21:35:42 -0000 Mailing-List: contact gdb-help@sources.redhat.com; run by ezmlm Precedence: bulk List-Subscribe: List-Archive: List-Post: List-Help: , Sender: gdb-owner@sources.redhat.com Received: (qmail 714 invoked from network); 1 Dec 2002 21:35:41 -0000 Received: from unknown (HELO crack.them.org) (65.125.64.184) by sources.redhat.com with SMTP; 1 Dec 2002 21:35:41 -0000 Received: from nevyn.them.org ([66.93.61.169] ident=mail) by crack.them.org with asmtp (Exim 3.12 #1 (Debian)) id 18Idcx-0001ey-00; Sun, 01 Dec 2002 17:35:55 -0600 Received: from drow by nevyn.them.org with local (Exim 3.36 #1 (Debian)) id 18Ibkp-0003Wz-00; Sun, 01 Dec 2002 16:35:55 -0500 Date: Sun, 01 Dec 2002 13:35:00 -0000 From: Daniel Jacobowitz To: Richard Brunelle Cc: gdb@sources.redhat.com Subject: Re: Ctrl-c problem Message-ID: <20021201213555.GA13484@nevyn.them.org> Mail-Followup-To: Richard Brunelle , gdb@sources.redhat.com References: <3DE7D702.903@envitech.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <3DE7D702.903@envitech.com> User-Agent: Mutt/1.5.1i X-SW-Source: 2002-12/txt/msg00005.txt.bz2 On Fri, Nov 29, 2002 at 04:07:14PM -0500, Richard Brunelle wrote: > Hi, > > I'm doing kernel debugging through the use of gdb running on a > development machine and a gdb stub running on a target machine. The > latter is acheive with the kgdb patch applied to a kernel 2.4.18. This > patch allows me to connect a development PC to a target PC through a > serial line. It allows me to remotely debug a patched kernel. The > connection works fine, I'm able to connect gdb to the target machine at > boot time (target remote /dev/tyS0). The problem is not hardware. I am > able to step in the kernel code at this time. After a few step, I resume > the execution of the kernel with the continue command. > > My problem comes when I want to stop the execution of the target kernel > with gdb. Usually Ctrl-c is used to stop the execution of the running > process. So I hit Ctrl-c but the kernel never stop. > > Is there any configuration for gdb to enable Ctrl-c? > > Does anyone ever experience this problem? What's your target platform? C-c works using the x86 KGDB stub. I don't know if it works on PowerPC, and it definitely doesn't work on MIPS. This is a stub question. -- Daniel Jacobowitz MontaVista Software Debian GNU/Linux Developer