From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <gdb-return-27999-listarch-gdb=sources.redhat.com@sourceware.org>
Received: (qmail 1073 invoked by alias); 6 Mar 2007 02:40:17 -0000
Received: (qmail 1064 invoked by uid 22791); 6 Mar 2007 02:40:17 -0000
X-Spam-Check-By: sourceware.org
Received: from rwcrmhc11.comcast.net (HELO rwcrmhc11.comcast.net) (216.148.227.151)     by sourceware.org (qpsmtpd/0.31) with ESMTP; Tue, 06 Mar 2007 02:40:14 +0000
Received: from [172.22.0.103] (failure[71.63.50.10])           by comcast.net (rwcrmhc11) with ESMTP           id <20070306024011m11009q0mje>; Tue, 6 Mar 2007 02:40:12 +0000
Message-ID: <45ECD480.9020901@ringle.org>
Date: Tue, 06 Mar 2007 02:40:00 -0000
From: Jon Ringle <jon@ringle.org>
User-Agent: Thunderbird 1.5.0.10 (Windows/20070221)
MIME-Version: 1.0
To: Michael Snyder <Michael.Snyder@palmsource.com>
CC:  gdb@sourceware.org
Subject: Re: [SPAM]  Re: gdbserver signals interfere with {next,step{,i}}
References: <45EC780E.60705@ringle.org>	 <20070305201726.GA11385@caradoc.them.org>  <45ECA592.5080802@ringle.org>	 <1173145366.29183.56.camel@localhost.localdomain>	 <45ECC84A.9020702@ringle.org> <1173147085.29183.61.camel@localhost.localdomain>
In-Reply-To: <1173147085.29183.61.camel@localhost.localdomain>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Mailing-List: contact gdb-help@sourceware.org; run by ezmlm
Precedence: bulk
List-Id: <gdb.sourceware.org>
List-Subscribe: <mailto:gdb-subscribe@sourceware.org>
List-Archive: <http://sourceware.org/ml/gdb/>
List-Post: <mailto:gdb@sourceware.org>
List-Help: <mailto:gdb-help@sourceware.org>, <http://sourceware.org/ml/#faqs>
Sender: gdb-owner@sourceware.org
X-SW-Source: 2007-03/txt/msg00077.txt.bz2

Michael Snyder wrote:
> OK, I built it with arm-linux-gcc -lrt -lpthread -g 
>
> I copied it to my arm dev board running kernel 2.6.14
> (intel Zylonite)
>
> I started it under gdbserver 6.5, connected to it with gdb 6.5, 
> break on line 106 as suggested by the comment, gave it some 
> input, hit the breakpoint, nexted a few times...
>
> I didn't see any odd behavior (I also didn't see gdb report any
> SIGUSR1 events).
>
>   
Did you do a 'handle SIGUSR1 nostop noprint' to avoid seeing SIGUSR1 events?
Did the "Prompt %d" increment as you proceeded with the test?

Other details about my target: linux 2.6.16.29, uclibc-0.9.28, gdbserver 
6.6, gdb 6.6, armeb-linux-gcc 3.4.6

Jon