From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 118442 invoked by alias); 27 May 2019 02:32:47 -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 118433 invoked by uid 89); 27 May 2019 02:32:46 -0000 Authentication-Results: sourceware.org; auth=none X-Spam-SWARE-Status: No, score=-3.1 required=5.0 tests=AWL,BAYES_00,SPF_PASS autolearn=ham version=3.3.1 spammy=HX-Languages-Length:842, saying, themselves, H*r:142 X-HELO: eggs.gnu.org Received: from eggs.gnu.org (HELO eggs.gnu.org) (209.51.188.92) by sourceware.org (qpsmtpd/0.93/v0.84-503-g423c35a) with ESMTP; Mon, 27 May 2019 02:32:45 +0000 Received: from fencepost.gnu.org ([2001:470:142:3::e]:58177) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1hV5RL-00017P-Ms; Sun, 26 May 2019 22:32:43 -0400 Received: from [176.228.60.248] (port=3832 helo=home-c4e4a596f7) by fencepost.gnu.org with esmtpsa (TLS1.2:RSA_AES_256_CBC_SHA1:256) (Exim 4.82) (envelope-from ) id 1hV5RL-0003l4-22; Sun, 26 May 2019 22:32:43 -0400 Date: Mon, 27 May 2019 02:32:00 -0000 Message-Id: <834l5g39v6.fsf@gnu.org> From: Eli Zaretskii To: Tom Tromey CC: gdb-patches@sourceware.org In-reply-to: <875zpxdjvv.fsf@tromey.com> (message from Tom Tromey on Sun, 26 May 2019 14:46:12 -0600) Subject: Re: [PATCH v2 8/8] Add maint set/show enable-threads References: <20190518210010.27697-1-tom@tromey.com> <20190518210010.27697-9-tom@tromey.com> <83pnob84lo.fsf@gnu.org> <875zpxdjvv.fsf@tromey.com> X-detected-operating-system: by eggs.gnu.org: GNU/Linux 2.2.x-3.x [generic] X-IsSubscribed: yes X-SW-Source: 2019-05/txt/msg00586.txt.bz2 > From: Tom Tromey > Cc: Tom Tromey , gdb-patches@sourceware.org > Date: Sun, 26 May 2019 14:46:12 -0600 > > >> +maint set enable-threads > >> +maint show enable-threads > >> + Control whether GDB can use threads. The default is "on". > > Eli> I'd suggest to say what will threads be used for. > > In NEWS I guess it's ok, but elsewhere I'd prefer to be a bit vague > about the precise use of threads. That way the documentation won't go > stale if we add more uses. That's okay, we can be vague. How about saying that "threads are used for some CPU-extensive processing, such as ..." and give one example? My point is that leaving it entirely unsaid is way too vague, especially for readers who might be debugging programs that themselves use threads.