From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 23286 invoked by alias); 6 Mar 2007 02:11:47 -0000 Received: (qmail 23181 invoked by uid 22791); 6 Mar 2007 02:11:46 -0000 X-Spam-Check-By: sourceware.org Received: from mx2.palmsource.com (HELO mx2.palmsource.com) (12.7.175.14) by sourceware.org (qpsmtpd/0.31) with ESMTP; Tue, 06 Mar 2007 02:11:44 +0000 Received: from localhost (localhost [127.0.0.1]) by localhost.domain.tld (Postfix) with ESMTP id E5E4C13769F; Mon, 5 Mar 2007 18:11:33 -0800 (PST) Received: from mx2.palmsource.com ([127.0.0.1]) by localhost (mx2.palmsource.com [127.0.0.1]) (amavisd-new, port 10024) with LMTP id 10416-02-3; Mon, 5 Mar 2007 18:11:32 -0800 (PST) Received: from ussunex01.palmsource.com (unknown [192.168.101.9]) by mx2.palmsource.com (Postfix) with ESMTP id 3E7AF13717D; Mon, 5 Mar 2007 18:11:27 -0800 (PST) Received: from 192.168.92.81 ([192.168.92.81]) by ussunex01.palmsource.com ([192.168.101.9]) via Exchange Front-End Server owa.palmsource.com ([10.0.20.17]) with Microsoft Exchange Server HTTP-DAV ; Tue, 6 Mar 2007 02:11:27 +0000 Received: from svmsnyderlnx by owa.palmsource.com; 05 Mar 2007 18:11:25 -0800 Subject: Re: gdbserver signals interfere with {next,step{,i}} From: Michael Snyder To: Jon Ringle Cc: gdb@sourceware.org In-Reply-To: <45ECC84A.9020702@ringle.org> References: <45EC780E.60705@ringle.org> <20070305201726.GA11385@caradoc.them.org> <45ECA592.5080802@ringle.org> <1173145366.29183.56.camel@localhost.localdomain> <45ECC84A.9020702@ringle.org> Content-Type: text/plain Content-Transfer-Encoding: 7bit Date: Tue, 06 Mar 2007 02:11:00 -0000 Message-Id: <1173147085.29183.61.camel@localhost.localdomain> Mime-Version: 1.0 X-Mailer: Evolution 2.4.1 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/msg00075.txt.bz2 On Mon, 2007-03-05 at 20:47 -0500, Jon Ringle wrote: > Michael Snyder wrote: > >>> Attached is a test case. > >>> > > > > What library do I link to for timer_create? > > > > > > > This is how I built the testcase: > $ CC=armeb-linux-gcc LDFLAGS="-lrt -lpthread" CFLAGS="-g" make > gdbsignal-test 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).