From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 21938 invoked by alias); 21 May 2019 00:35:08 -0000 Mailing-List: contact gdb-patches-help@sourceware.org; run by ezmlm Precedence: bulk List-Id: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: gdb-patches-owner@sourceware.org Received: (qmail 21929 invoked by uid 89); 21 May 2019 00:35:08 -0000 Authentication-Results: sourceware.org; auth=none X-Spam-SWARE-Status: No, score=-8.8 required=5.0 tests=AWL,BAYES_00,RCVD_IN_DNSWL_LOW,SPF_PASS autolearn=ham version=3.3.1 spammy= X-HELO: mailsec111.isp.belgacom.be Received: from mailsec111.isp.belgacom.be (HELO mailsec111.isp.belgacom.be) (195.238.20.107) by sourceware.org (qpsmtpd/0.93/v0.84-503-g423c35a) with ESMTP; Tue, 21 May 2019 00:35:04 +0000 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=skynet.be; i=@skynet.be; q=dns/txt; s=securemail; t=1558398905; x=1589934905; h=message-id:subject:from:to:cc:date:in-reply-to: references:mime-version:content-transfer-encoding; bh=zs/Q5gPtwiEDZ2VhvGRD7dU6rq759/AM26pCZihSnBU=; b=0azqyODEiKxa/uqfy3SbKoPdKB8boRJIt8b2W3QTP/+NR61bBlGC5vVy UbDZcAFbPM0uHfjRBwAbmsy/cCzwpQ==; Received: from 161.32-242-81.adsl-dyn.isp.belgacom.be (HELO md) ([81.242.32.161]) by relay.skynet.be with ESMTP/TLS/AES256-GCM-SHA384; 21 May 2019 02:35:02 +0200 Message-ID: <1558398902.1454.16.camel@skynet.be> Subject: Re: [PATCH v2 0/8] Demangle minimal symbol names in worker threads From: Philippe Waroquiers To: Tom Tromey Cc: gdb-patches@sourceware.org Date: Tue, 21 May 2019 00:35:00 -0000 In-Reply-To: <87a7figtpz.fsf@tromey.com> References: <20190518210010.27697-1-tom@tromey.com> <1558274338.1454.13.camel@skynet.be> <87a7figtpz.fsf@tromey.com> Content-Type: text/plain; charset="UTF-8" Mime-Version: 1.0 Content-Transfer-Encoding: 7bit X-IsSubscribed: yes X-SW-Source: 2019-05/txt/msg00464.txt.bz2 On Sun, 2019-05-19 at 12:55 -0600, Tom Tromey wrote: > Philippe> One comment about 'maint set|show enable-threads' : > Philippe> what is the reason to have this as a maintenance command ? > > I see it as a setting for gdb developers, not gdb users. In fact, v1 > didn't have this, but John wanted a way to disable threading for > debugging gdb. > > Philippe> Also, maybe it would be better to have this setting being the > Philippe> maximum nr of threads to use. In some environments (e.g. > Philippe> operational environments), one might want to limit the nr of threads > Philippe> used by GDB. > > I think that most users don't know what most programs do under the hood; > nor should they need to. I suppose in some extreme situation maybe > someone would want to do this, but disabling threading in this case > should be good enough. Users like this should probably use gdbserver > instead though. It looks relatively common to let the end user control the level of parallelism. E.g. xz, make, gnatmake, firefox all have a way to let the user tune the parallelism (nr of processes or threads). Philippe