From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 19738 invoked by alias); 2 Dec 2002 17:27:35 -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 19730 invoked from network); 2 Dec 2002 17:27:35 -0000 Received: from unknown (HELO relais.progression.net) (207.253.63.13) by sources.redhat.com with SMTP; 2 Dec 2002 17:27:35 -0000 Received: from envitech.com (usrppp165.progression.net [207.253.63.165]) by relais.progression.net (8.11.6/8.11.6) with ESMTP id gB2HRVu24053; Mon, 2 Dec 2002 12:27:32 -0500 Message-ID: <3DEB975E.4050200@envitech.com> Date: Mon, 02 Dec 2002 09:27:00 -0000 From: Richard Brunelle 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: Daniel Jacobowitz CC: gdb@sources.redhat.com Subject: Re: Ctrl-c problem References: <3DE7D702.903@envitech.com> <20021201213555.GA13484@nevyn.them.org> <3DEB878D.8000403@envitech.com> <20021202162534.GA11654@nevyn.them.org> <3DEB920F.5010803@envitech.com> <20021202171836.GA13745@nevyn.them.org> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit X-SW-Source: 2002-12/txt/msg00016.txt.bz2 That was the problem. You are right, miss-configuration problem, not a gdb bug. Daniel Jacobowitz wrote: >Sure, it's possible. You should probably have console and KGDB >configured for different ports... > >In any case, not a GDB bug. > >On Mon, Dec 02, 2002 at 12:02:07PM -0500, Richard Brunelle wrote: > > >>I tried echoing '\003' and I still can't stop it. >> >>I'm wondering if the problem doesn't come when the boot resumed. After >>the boot procedure is completed, is there a chance that the serial port >>used on the target machine be re-configured to a different baud rate? >> >>Daniel Jacobowitz wrote: >> >> >> >>>Then it should work if you are using any current KGDB patch. You can >>>try echoing '\003' out the serial port (echo '\003' > /dev/ttyS0) and >>>see if that stops it. >>> >>>On Mon, Dec 02, 2002 at 11:17:17AM -0500, Richard Brunelle wrote: >>> >>> >>> >>> >>>>My target platform is a x86 single board computer running a PentiumMMX @ >>>>266 MHz. >>>>Its seen as a standard PC with extra hardware on it (analog to digital >>>>converter). >>>> >>>>Daniel Jacobowitz wrote: >>>> >>>> >>>> >>>> >>>> >>>>>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. >>>>> >>>>> >>>>> >>>>> >>>>> >>>>> >>>>> >>>> >>>> >>>> >>>> >>> >>> >>> >> >> >> > > >