From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 31995 invoked by alias); 16 May 2006 18:25:32 -0000 Received: (qmail 31979 invoked by uid 22791); 16 May 2006 18:25:32 -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; Tue, 16 May 2006 18:25:29 +0000 Received: from drow by nevyn.them.org with local (Exim 4.54) id 1Fg4EX-0002VM-5d; Tue, 16 May 2006 14:25:25 -0400 Date: Tue, 16 May 2006 19:05:00 -0000 From: Daniel Jacobowitz To: Mark Kettenis Cc: milrith@gmail.com, gdb@sourceware.org Subject: Re: Problems with remote debugging on ARM Message-ID: <20060516182525.GA9596@nevyn.them.org> Mail-Followup-To: Mark Kettenis , milrith@gmail.com, gdb@sourceware.org References: <20060516180820.1dcb8eb4.milrith@gmail.com> <20060516161319.GA4329@nevyn.them.org> <200605161818.k4GII5Ai006194@elgar.sibelius.xs4all.nl> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <200605161818.k4GII5Ai006194@elgar.sibelius.xs4all.nl> User-Agent: Mutt/1.5.11+cvs20060403 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-05/txt/msg00241.txt.bz2 On Tue, May 16, 2006 at 08:18:05PM +0200, Mark Kettenis wrote: > > Date: Tue, 16 May 2006 12:13:19 -0400 > > From: Daniel Jacobowitz > > > > On Tue, May 16, 2006 at 06:08:20PM +0200, Milrith wrote: > > > I use a timer which is generating a signal every 10 ms (SIGALRM). As > > > soon as timer_settime is called, there is a lot of network activity, > > > the gdb client seems to be busy (when I step) and debugging is unusable. > > > If i increase the period of this timer (to something like 50 ms) it is > > > OK. Would there be a means to still be able to debug my program with > > > the 10 ms period? > > > > Right now there is no way to do this. I had a patch for it long ago, > > but it wasn't very nice, and I never had time to go back to it. You > > could hack your GDB stub to ignore SIGALRM, in the same way that it > > ignores certain threading-related signals (assuming you're using > > gdbserver). > > Actually it wouldn't be such a bad idea to extend the remote protocol > with something that allows GDB to specify the signals it's interested > in. Ultimately you want this in the OS such that the stub (or a > native GDB) never even sees the signal. Solaris and HP-UX have that > functionality. That is precisely what I did :-) -- Daniel Jacobowitz CodeSourcery