From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 10557 invoked by alias); 6 Mar 2007 19:46:26 -0000 Received: (qmail 10549 invoked by uid 22791); 6 Mar 2007 19:46:25 -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 19:46:15 +0000 Received: from localhost (localhost [127.0.0.1]) by localhost.domain.tld (Postfix) with ESMTP id 45600135512; Tue, 6 Mar 2007 11:46:14 -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 14572-01-6; Tue, 6 Mar 2007 11:46:13 -0800 (PST) Received: from ussunex01.palmsource.com (unknown [192.168.101.9]) by mx2.palmsource.com (Postfix) with ESMTP id 4F5601354EC; Tue, 6 Mar 2007 11:46:13 -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 19:46:12 +0000 Received: from svmsnyderlnx by owa.palmsource.com; 06 Mar 2007 11:46:11 -0800 Subject: Re: [SPAM] Re: gdbserver signals interfere with {next,step{,i}} From: Michael Snyder To: Jon Ringle Cc: gdb@sourceware.org, Daniel Jacobowitz In-Reply-To: <45ED7B32.5060100@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> <1173147085.29183.61.camel@localhost.localdomain> <45ECD0DE.206@ringle.org> <20070306122541.GA1414@caradoc.them.org> <45ED7B32.5060100@ringle.org> Content-Type: text/plain Content-Transfer-Encoding: 7bit Date: Tue, 06 Mar 2007 19:46:00 -0000 Message-Id: <1173210371.29183.101.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/msg00103.txt.bz2 On Tue, 2007-03-06 at 09:31 -0500, Jon Ringle wrote: > Daniel Jacobowitz wrote: > > On Mon, Mar 05, 2007 at 09:24:30PM -0500, Jon Ringle wrote: > > > >> My target uses uclibc-0.9.28 rather than a glibc libc. Could that be a > >> factor here? > >> > > > > Yes, it certainly could be. > > > > > When I use a native gdb-6.6 on the uclibc target, I don't see any > SIGUSR1 signals being intercepted by gdb (so I don't have to do 'handle > SIGUSR1 nostop noprint') and I see correct behaviour using 'next'. Important question -- does gdb thread support (either native or remote/gdbserver) work at all with uclibc?