From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 29180 invoked by alias); 15 Jun 2009 16:51:12 -0000 Received: (qmail 29170 invoked by uid 22791); 15 Jun 2009 16:51:11 -0000 X-SWARE-Spam-Status: No, hits=-2.5 required=5.0 tests=AWL,BAYES_00 X-Spam-Check-By: sourceware.org Received: from NaN.false.org (HELO nan.false.org) (208.75.86.248) by sourceware.org (qpsmtpd/0.43rc1) with ESMTP; Mon, 15 Jun 2009 16:51:05 +0000 Received: from nan.false.org (localhost [127.0.0.1]) by nan.false.org (Postfix) with ESMTP id 61FD610DC5; Mon, 15 Jun 2009 16:51:03 +0000 (GMT) Received: from caradoc.them.org (209.195.188.212.nauticom.net [209.195.188.212]) by nan.false.org (Postfix) with ESMTP id 2870E10A42; Mon, 15 Jun 2009 16:51:03 +0000 (GMT) Received: from drow by caradoc.them.org with local (Exim 4.69) (envelope-from ) id 1MGFOg-00046y-57; Mon, 15 Jun 2009 12:51:02 -0400 Date: Mon, 15 Jun 2009 16:51:00 -0000 From: Daniel Jacobowitz To: suresh ds Cc: Pedro Alves , gdb@sourceware.org Subject: Re: Behaviour of default all-stop mode -- Why no one has replied ? Message-ID: <20090615165102.GA15784@caradoc.them.org> Mail-Followup-To: suresh ds , Pedro Alves , gdb@sourceware.org References: <20090615153658.A0684606884@ws1-4.us4.outblaze.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20090615153658.A0684606884@ws1-4.us4.outblaze.com> User-Agent: Mutt/1.5.17 (2008-05-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: 2009-06/txt/msg00148.txt.bz2 On Mon, Jun 15, 2009 at 10:36:58AM -0500, suresh ds wrote: > Thanks Daniel. > I'm still expecting answers for my other queries. > 1) When I continue, gdb sends packet only to resume one (current) thread. How to make gdb send packets to resume other threads ? > Even if I 'switch' to other thread, and continue, it still keeps sending packets only to the previously set thread. > > 2) Through 'Thread apply' or Thread-specific breakpoints' also, I'm not able to make gdb send packets to resume threads. > > How to achieve this ? I don't know, but you may want to investigate the scheduler-locking setting. Also, don't be fooled by GDB's behavior when there is a breakpoint at the current address; that's a special case that trips up a lot of people. Look at the following vCont after GDB has navigated off the breakpoint. -- Daniel Jacobowitz CodeSourcery