From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 12750 invoked by alias); 29 Nov 2007 08:36:11 -0000 Received: (qmail 12742 invoked by uid 22791); 29 Nov 2007 08:36:10 -0000 X-Spam-Check-By: sourceware.org Received: from main.gmane.org (HELO ciao.gmane.org) (80.91.229.2) by sourceware.org (qpsmtpd/0.31) with ESMTP; Thu, 29 Nov 2007 08:36:01 +0000 Received: from list by ciao.gmane.org with local (Exim 4.43) id 1Ixeq9-0000n1-SH for gdb@sources.redhat.com; Thu, 29 Nov 2007 08:34:15 +0000 Received: from 77.246.241.246 ([77.246.241.246]) by main.gmane.org with esmtp (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Thu, 29 Nov 2007 08:33:45 +0000 Received: from ghost by 77.246.241.246 with local (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Thu, 29 Nov 2007 08:33:45 +0000 To: gdb@sources.redhat.com From: Vladimir Prus Subject: Re: Non-stop multi-threaded debugging Date: Thu, 29 Nov 2007 08:36:00 -0000 Message-ID: References: <474CFA34.1030309@windriver.com> <18254.7923.167270.745538@kahikatea.snap.net.nz> <474E58EF.2060601@windriver.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7Bit User-Agent: KNode/0.10.4 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-11/txt/msg00268.txt.bz2 Pawel Piech wrote: > Nick Roberts wrote: >> > ... A -thread-select on an >> > ID of a process followed by an -exec-continue would resume an entire >> > process, while a -thread-select of a thread's ID followed by a >> > continue >> > would resume only that thread. This could also be applied to all >> > other commands that need to operate on a process, such as >> > -thread-list-ids, -break-insert, etc. >> >> This would change the current behaviour of these commands. If a new >> command is undesirable then perhaps optional parameters could be used: >> >> -exec-continue [ -p THREAD-ID/PROCESS-ID ] >> -exec-interrupt [ -p THREAD-ID/PROCESS-ID ] >> >> It appears that -break-insert already has such an option for threads. >> >> > From Eclipse's point of view it actually doesn't make much difference > whether -thread-select or -p option is used to specify the thread. > > That said, I would argue that adding the non-stop debugging feature > changes the behavior of the entire system, so it could be expected that > some commands will behave somewhat differently as they relate to this > new feature. Actually, with non-stop debugging feature turned off, and > without attaching to multiple processes, these commands would still > behave exactly as they do now. Given the choice between: 1. Changing the behaviour of the existing command, and adding new one that behaves like existing one, and 2. Adding new command I think adding new command (or option to existing command), is a smaller change. So yes, -exec-continue -t might be a better choice. - Volodya