From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 14822 invoked by alias); 22 Feb 2006 04:40:13 -0000 Received: (qmail 14814 invoked by uid 22791); 22 Feb 2006 04:40:12 -0000 X-Spam-Check-By: sourceware.org Received: from nevyn.them.org (HELO nevyn.them.org) (66.93.172.17) by sourceware.org (qpsmtpd/0.31.1) with ESMTP; Wed, 22 Feb 2006 04:40:11 +0000 Received: from drow by nevyn.them.org with local (Exim 4.54) id 1FBlnN-0002ki-Kq; Tue, 21 Feb 2006 23:40:09 -0500 Date: Wed, 22 Feb 2006 06:23:00 -0000 From: Daniel Jacobowitz To: Pedro Alves Cc: gdb@sourceware.org Subject: Re: gdb on arm-wince-pe Message-ID: <20060222044009.GB10442@nevyn.them.org> Mail-Followup-To: Pedro Alves , gdb@sourceware.org References: <43FB7B0C.2010703@portugalmail.pt> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <43FB7B0C.2010703@portugalmail.pt> User-Agent: Mutt/1.5.8i X-IsSubscribed: yes Mailing-List: contact gdb-help@sourceware.org; run by ezmlm Precedence: bulk List-Subscribe: List-Archive: List-Post: List-Help: , Sender: gdb-owner@sourceware.org X-SW-Source: 2006-02/txt/msg00289.txt.bz2 On Tue, Feb 21, 2006 at 08:41:48PM +0000, Pedro Alves wrote: > Where should I start looking for/what is needed to implement it (ctrl_c > breaking)? > I tried debugging arm-wince-pe-gdb on gdb itself, putting some > breakpoints in the signal handling, > and issuing kill -INT signals to see what happens there, and I see that > ultimatly, quit (void) is called. > Is there some target_op that I should implement, or should I provide my > own signal handling? Take a look at remote.c, which installs its own signal handler. You'll want to do something similar. Really, if possible, I would recommend using remote.c to talk to your target over the standard GDB remote protocol instead of the WinCE-specific protocol that wince-stub.c implements. That's much better supported. -- Daniel Jacobowitz CodeSourcery