From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 13771 invoked by alias); 16 May 2006 19:03:00 -0000 Received: (qmail 13757 invoked by uid 22791); 16 May 2006 19:02:56 -0000 X-Spam-Check-By: sourceware.org Received: from nf-out-0910.google.com (HELO nf-out-0910.google.com) (64.233.182.189) by sourceware.org (qpsmtpd/0.31) with ESMTP; Tue, 16 May 2006 19:02:29 +0000 Received: by nf-out-0910.google.com with SMTP id n29so36109nfc for ; Tue, 16 May 2006 12:02:26 -0700 (PDT) Received: by 10.49.18.1 with SMTP id v1mr58954nfi; Tue, 16 May 2006 12:02:26 -0700 (PDT) Received: from localhost ( [82.73.179.23]) by mx.gmail.com with ESMTP id r33sm180673nfc.2006.05.16.12.02.17; Tue, 16 May 2006 12:02:25 -0700 (PDT) Date: Tue, 16 May 2006 19:25:00 -0000 From: Milrith To: gdb@sourceware.org Subject: Re: Problems with remote debugging on ARM Message-Id: <20060516205958.beae8e7b.milrith@gmail.com> In-Reply-To: <20060516161319.GA4329@nevyn.them.org> References: <20060516180820.1dcb8eb4.milrith@gmail.com> <20060516161319.GA4329@nevyn.them.org> X-Mailer: Sylpheed version 2.2.4 (GTK+ 2.8.17; i486-pc-linux-gnu) Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-15 Content-Transfer-Encoding: quoted-printable 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/msg00242.txt.bz2 Le Tue, 16 May 2006 12:13:19 -0400 Daniel Jacobowitz a =E9crit=A0:=20 > 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? >=20 > 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). Yes, I am using gdbserver. Right now SIGALRM is treated as pass noprint nostop. Would you have more details on how to do this hack? ;) > > I have problems with breakpoints not taken into account, are there > > known problems with some parts of my configuration (C++ or threads)? >=20 > Are they in constructors? Google would be glad to tell you about the > problem, in that case. Unfortunately not, it can happen in normal methods. I am compiling with -g and without any optimisation option. Another little problem: I can't autocomplete method names with "::" after the class names (Class:: produces nothing), I suppose I am missing a little something? Thanks a lot, Milrith