From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 28675 invoked by alias); 16 May 2006 18:18:48 -0000 Received: (qmail 28667 invoked by uid 22791); 16 May 2006 18:18:47 -0000 X-Spam-Check-By: sourceware.org Received: from sibelius.xs4all.nl (HELO sibelius.xs4all.nl) (82.92.89.47) by sourceware.org (qpsmtpd/0.31) with ESMTP; Tue, 16 May 2006 18:18:44 +0000 Received: from elgar.sibelius.xs4all.nl (root@elgar.sibelius.xs4all.nl [192.168.0.2]) by sibelius.xs4all.nl (8.13.4/8.13.4) with ESMTP id k4GII6QR015020; Tue, 16 May 2006 20:18:06 +0200 (CEST) Received: from elgar.sibelius.xs4all.nl (kettenis@localhost.sibelius.xs4all.nl [127.0.0.1]) by elgar.sibelius.xs4all.nl (8.13.6/8.13.6) with ESMTP id k4GII61u016857; Tue, 16 May 2006 20:18:06 +0200 (CEST) Received: (from kettenis@localhost) by elgar.sibelius.xs4all.nl (8.13.6/8.13.6/Submit) id k4GII5Ai006194; Tue, 16 May 2006 20:18:05 +0200 (CEST) Date: Tue, 16 May 2006 19:03:00 -0000 Message-Id: <200605161818.k4GII5Ai006194@elgar.sibelius.xs4all.nl> From: Mark Kettenis To: drow@false.org CC: milrith@gmail.com, gdb@sourceware.org In-reply-to: <20060516161319.GA4329@nevyn.them.org> (message from Daniel Jacobowitz on Tue, 16 May 2006 12:13:19 -0400) Subject: Re: Problems with remote debugging on ARM References: <20060516180820.1dcb8eb4.milrith@gmail.com> <20060516161319.GA4329@nevyn.them.org> 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/msg00240.txt.bz2 > 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. Mark