From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 29767 invoked by alias); 5 Mar 2007 20:17:38 -0000 Received: (qmail 29737 invoked by uid 22791); 5 Mar 2007 20:17:37 -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; Mon, 05 Mar 2007 20:17:30 +0000 Received: from dsl093-172-095.pit1.dsl.speakeasy.net ([66.93.172.95] helo=caradoc.them.org) by nevyn.them.org with esmtp (Exim 4.63) (envelope-from ) id 1HOJcd-0002Vk-Aw; Mon, 05 Mar 2007 15:17:27 -0500 Received: from drow by caradoc.them.org with local (Exim 4.63) (envelope-from ) id 1HOJcc-0002xz-Ua; Mon, 05 Mar 2007 15:17:26 -0500 Date: Mon, 05 Mar 2007 20:17:00 -0000 From: Daniel Jacobowitz To: Jon Ringle Cc: gdb@sourceware.org Subject: Re: gdbserver signals interfere with {next,step{,i}} Message-ID: <20070305201726.GA11385@caradoc.them.org> Mail-Followup-To: Jon Ringle , gdb@sourceware.org References: <45EC780E.60705@ringle.org> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <45EC780E.60705@ringle.org> User-Agent: Mutt/1.5.13 (2006-08-11) X-IsSubscribed: yes Mailing-List: contact gdb-help@sourceware.org; run by ezmlm Precedence: bulk List-Id: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: gdb-owner@sourceware.org X-SW-Source: 2007-03/txt/msg00067.txt.bz2 On Mon, Mar 05, 2007 at 03:05:34PM -0500, Jon Ringle wrote: > Hello, > > I have an application that uses SIGUSR1 to receive timer interrupts. > I've done 'handle SIGUSR1 nostop noprint' to avoid gdb from stopping on > SIGUSR1. > I've found that when debugging this application using gdbserver, that I > can't use next, nexti, step, or stepi. When I use one of these commands, > the application usually just continues without stopping at the next > line/instruction. > > If I use a native gdb on the target the problem does not occur. > If I disable my app from generating the SIGUSR1 and use gdbserver, the > problem also goes away. I haven't seen this problem before. Can you make a small test case which demonstrates the problem, maybe? What target are you using? -- Daniel Jacobowitz CodeSourcery