From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <gdb-return-11336-listarch-gdb=sources.redhat.com@sources.redhat.com>
Received: (qmail 6090 invoked by alias); 29 Nov 2002 21:09:08 -0000
Mailing-List: contact gdb-help@sources.redhat.com; run by ezmlm
Precedence: bulk
List-Subscribe: <mailto:gdb-subscribe@sources.redhat.com>
List-Archive: <http://sources.redhat.com/ml/gdb/>
List-Post: <mailto:gdb@sources.redhat.com>
List-Help: <mailto:gdb-help@sources.redhat.com>, <http://sources.redhat.com/ml/#faqs>
Sender: gdb-owner@sources.redhat.com
Received: (qmail 6082 invoked from network); 29 Nov 2002 21:09:07 -0000
Received: from unknown (HELO relais.progression.net) (207.253.63.13)
  by sources.redhat.com with SMTP; 29 Nov 2002 21:09:07 -0000
Received: from envitech.com (usrppp175.progression.net [207.253.63.175])
	by relais.progression.net (8.11.6/8.11.6) with ESMTP id gATL95u30528
	for <gdb@sources.redhat.com>; Fri, 29 Nov 2002 16:09:05 -0500
Message-ID: <3DE7D702.903@envitech.com>
Date: Fri, 29 Nov 2002 13:09:00 -0000
From: Richard Brunelle <rbrunelle@envitech.com>
Reply-To: rbrunelle@envitech.com
Organization: Envitech Automation
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.0.0) Gecko/20020623 Debian/1.0.0-0.woody.1
X-Accept-Language: en
MIME-Version: 1.0
To: gdb@sources.redhat.com
Subject: Ctrl-c problem
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
X-SW-Source: 2002-11/txt/msg00433.txt.bz2

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?

Richard Brunelle