From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 13614 invoked by alias); 15 Jun 2009 15:37:09 -0000 Received: (qmail 13585 invoked by uid 22791); 15 Jun 2009 15:37:08 -0000 X-SWARE-Spam-Status: No, hits=-2.0 required=5.0 tests=AWL,BAYES_00 X-Spam-Check-By: sourceware.org Received: from outbound1-1.us4.outblaze.com (HELO outbound1-1.us4.outblaze.com) (208.36.123.129) by sourceware.org (qpsmtpd/0.43rc1) with ESMTP; Mon, 15 Jun 2009 15:37:00 +0000 Received: from wfilter3.us4.outblaze.com.int (wfilter3.us4.outblaze.com.int [192.168.8.242]) by outbound1-1.us4.outblaze.com (Postfix) with QMQP id B2CE17A0F26 for ; Mon, 15 Jun 2009 15:36:58 +0000 (GMT) X-OB-Received: from unknown (205.158.62.50) by wfilter3.us4.outblaze.com; 15 Jun 2009 15:36:58 -0000 Received: by ws1-4.us4.outblaze.com (Postfix, from userid 1001) id A0684606884; Mon, 15 Jun 2009 15:36:58 +0000 (GMT) Content-Disposition: inline Content-Transfer-Encoding: quoted-printable Content-Type: text/plain; charset="iso-8859-1" MIME-Version: 1.0 From: "suresh ds" To: "Daniel Jacobowitz" Cc: "Pedro Alves" , gdb@sourceware.org Date: Mon, 15 Jun 2009 15:37:00 -0000 Subject: Re: Behaviour of default all-stop mode -- Why no one has replied ? Received: from [203.92.57.132] by ws1-4.us4.outblaze.com with http for dssuresh66@mail.com; Mon, 15 Jun 2009 10:36:58 -0500 X-Ob-Auth: dssuresh66:mail.com@mail.com Message-Id: <20090615153658.A0684606884@ws1-4.us4.outblaze.com> 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/msg00146.txt.bz2 Thanks Daniel. I'm still expecting answers for my other queries. 1) When I continue, gdb sends packet only to resume one (current) thread. H= ow to make gdb send packets to resume other threads ? Even if I 'switch' to other thread, and continue, it still keeps sending pa= ckets only to the previously set thread. 2) Through 'Thread apply' or Thread-specific breakpoints' also, I'm not abl= e to make gdb send packets to resume threads. How to achieve this ? Thanks, Suresh ----- Original Message ----- From: "Daniel Jacobowitz"=20 To: "suresh ds"=20 Cc: "Pedro Alves" , gdb@sourceware.org Subject: Re: Behaviour of default all-stop mode -- Why no one has replied ? Date: Mon, 15 Jun 2009 11:20:10 -0400 On Mon, Jun 15, 2009 at 10:09:44AM -0500, suresh ds wrote: > Then I switched to thread 1. I really a have a big requirement from > the gdb developers here. Once I switch to a thread, ideally I expect > all further commands to apply only to that thread; It makes life > simple, isn't it ? This is non-stop mode. You need a GDB that supports non-stop mode for your processor in order to do this. GDB 6.8 doesn't support non-stop at all. GDB in CVS doesn't support non-stop for MIPS yet, I believe. -- Daniel Jacobowitz CodeSourcery --=20 Be Yourself @ mail.com! Choose From 200+ Email Addresses Get a Free Account at www.mail.com