From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 20479 invoked by alias); 29 Nov 2007 16:46:37 -0000 Received: (qmail 20471 invoked by uid 22791); 29 Nov 2007 16:46:36 -0000 X-Spam-Check-By: sourceware.org Received: from mail.codesourcery.com (HELO mail.codesourcery.com) (65.74.133.4) by sourceware.org (qpsmtpd/0.31) with ESMTP; Thu, 29 Nov 2007 16:46:31 +0000 Received: (qmail 25675 invoked from network); 29 Nov 2007 16:46:29 -0000 Received: from unknown (HELO 172.16.unknown.plus.ru) (vladimir@127.0.0.2) by mail.codesourcery.com with ESMTPA; 29 Nov 2007 16:46:29 -0000 From: Vladimir Prus To: Pawel Piech Subject: Re: Non-stop multi-threaded debugging Date: Thu, 29 Nov 2007 16:46:00 -0000 User-Agent: KMail/1.9.6 Cc: gdb@sourceware.org References: <474CFA34.1030309@windriver.com> <474EEB36.1040203@windriver.com> In-Reply-To: <474EEB36.1040203@windriver.com> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200711291946.25035.vladimir@codesourcery.com> 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/msg00276.txt.bz2 On Thursday 29 November 2007 19:39:18 Pawel Piech wrote: > I don't believe that I suggested adding any new command. > Instead, I suggested only changing the behavior of > some of the existing commands to use the currently selected thread. > It was Jim's proposal that included adding new commands. > My point was that instead of adding new commands it would be cleaner > to extend the functionality of -thread-select in order to select > a process context, i.e. a context that includes all threads. > This way existing commands, which currently can only operate > on a global context, could now operate on a process or a thread context. Ok, we have those choices: 1. Make -exec-continue work on all threads, until -thread-select is used. 2. Make -exec-continue work on one thread, and add another command to operate on all threads. 3. Make -exec-continue still operate on all threads, unless and explicit option to make it operate on a thread is given. You've indicated that (1) and (3) are about the same in complexity for you -- am I right? I personally prefer (3), since it does not implicitly changes the meaning of existing commands. Surely, non-stop mode does require some changes in frontend, but the fewer changes are, the better, IMO. - Volodya