From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 20107 invoked by alias); 2 Aug 2010 13:35:25 -0000 Received: (qmail 20095 invoked by uid 22791); 2 Aug 2010 13:35:24 -0000 X-SWARE-Spam-Status: No, hits=-2.0 required=5.0 tests=AWL,BAYES_00,T_RP_MATCHES_RCVD X-Spam-Check-By: sourceware.org Received: from mail.codesourcery.com (HELO mail.codesourcery.com) (38.113.113.100) by sourceware.org (qpsmtpd/0.43rc1) with ESMTP; Mon, 02 Aug 2010 13:35:19 +0000 Received: (qmail 28340 invoked from network); 2 Aug 2010 13:35:17 -0000 Received: from unknown (HELO orlando.localnet) (pedro@127.0.0.2) by mail.codesourcery.com with ESMTPA; 2 Aug 2010 13:35:17 -0000 From: Pedro Alves To: gdb@sourceware.org Subject: Re: Porting gdb to Cyclops64 Date: Mon, 02 Aug 2010 13:35:00 -0000 User-Agent: KMail/1.13.2 (Linux/2.6.31-11-rt; KDE/4.4.2; x86_64; ; ) Cc: Brian Heilig References: <1280510022.1560.20.camel@random> <201007310017.53475.pedro@codesourcery.com> <1280755494.1560.47.camel@random> In-Reply-To: <1280755494.1560.47.camel@random> MIME-Version: 1.0 Content-Type: Text/Plain; charset="utf-8" Content-Transfer-Encoding: 7bit Message-Id: <201008021435.16106.pedro@codesourcery.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: 2010-08/txt/msg00009.txt.bz2 On Monday 02 August 2010 14:24:54, Brian Heilig wrote: > On Sat, 2010-07-31 at 00:17 +0100, Pedro Alves wrote: > > Not sure what you mean --- the user would still have to resume each > > thread individually. But yes, in non-stop mode, your target should > > let the other threads that hadn't hit any breakpoint continue running > > free. > > My understanding is that in non-stop mode I can "continue all", whereas > in stop mode I can only continue the current thread. This would mean > that, in stop mode, each thread would have to be continued in > succession. In all-stop mode, what's resumed depends on the "set scheduler-locking" setting. By default, gdb tells the target to continue all threads (vCont;c). -- Pedro Alves