From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 66271 invoked by alias); 21 May 2019 16:21:26 -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 66260 invoked by uid 89); 21 May 2019 16:21:26 -0000 Authentication-Results: sourceware.org; auth=none X-Spam-SWARE-Status: No, score=-2.6 required=5.0 tests=AWL,BAYES_00,RCVD_IN_DNSWL_NONE,SPF_PASS autolearn=ham version=3.3.1 spammy=H*RU:209.85.128.68, HX-Spam-Relays-External:209.85.128.68 X-HELO: mail-wm1-f68.google.com Received: from mail-wm1-f68.google.com (HELO mail-wm1-f68.google.com) (209.85.128.68) by sourceware.org (qpsmtpd/0.93/v0.84-503-g423c35a) with ESMTP; Tue, 21 May 2019 16:21:25 +0000 Received: by mail-wm1-f68.google.com with SMTP id x64so3606875wmb.5 for ; Tue, 21 May 2019 09:21:24 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=embecosm.com; s=google; h=date:from:to:cc:subject:message-id:references:mime-version :content-disposition:in-reply-to:user-agent; bh=JykwyTBz0iwjvduptAoH0f+tIrRJb4f99+NoYdUlR+0=; b=IkTSKdtIdPoASgXolX8q67UHim0M3a8q3NudNLxGuLQERokF6AiOGPKROcX4ym7qz/ n4OAHP6+X83SIqb3ZwVaP+yYm2hT2DMKe8lxqe8vod/jbe5RS4cZcsev72wE27xXmUJt nspcor8cnaQlRSqnWWIBtD6ZpYjGET/4g7OcY7ao3q8Jyzlyf3vMNfDjnPmhEpyMgYom yfrBMcALhAvy5NT2OpnS3C3qca40VpCeEgGS90bWVm3JFfEMm9D6WyIJPdKiDQqxWbQr hWMFTJf8Jt6b141JlxBcaNxoXHLZthvK1wWgm5xr5LqH9zJvuIGrOC9KZVhxbyKZnt49 GRag== Return-Path: Received: from localhost (cust64-dsl91-135-5.idnet.net. [91.135.5.64]) by smtp.gmail.com with ESMTPSA id 20sm4731354wmj.36.2019.05.21.09.21.21 (version=TLS1_2 cipher=ECDHE-RSA-CHACHA20-POLY1305 bits=256/256); Tue, 21 May 2019 09:21:22 -0700 (PDT) Date: Tue, 21 May 2019 16:21:00 -0000 From: Andrew Burgess To: Tom Tromey Cc: Philippe Waroquiers , gdb-patches@sourceware.org Subject: Re: [PATCH v2 0/8] Demangle minimal symbol names in worker threads Message-ID: <20190521162121.GE2568@embecosm.com> References: <20190518210010.27697-1-tom@tromey.com> <1558274338.1454.13.camel@skynet.be> <87a7figtpz.fsf@tromey.com> <20190521073520.GD2568@embecosm.com> <87a7ffg6b2.fsf@tromey.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <87a7ffg6b2.fsf@tromey.com> X-Fortune: Never trust a child farther than you can throw it. X-Editor: GNU Emacs [ http://www.gnu.org/software/emacs ] User-Agent: Mutt/1.9.2 (2017-12-15) X-IsSubscribed: yes X-SW-Source: 2019-05/txt/msg00476.txt.bz2 * Tom Tromey [2019-05-21 11:45:21 -0400]: > >>>>> "Andrew" == Andrew Burgess writes: > > >> 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. > > Andrew> Sorry for being really slow, but how does gdbserver help here? The > Andrew> threads are to help GDB parse the symbols/debug information from the > Andrew> ELF, right? In most cases GDB will still be parsing the symbols/debug > Andrew> from the ELF at the GDB end, not the gdbserver end. > > My understanding is that the scenario is wanting to limit threads so > that one can run gdb on some resource-constrained machine. In this > situation it's better to run gdbserver on the limited machine and run > gdb on one's desktop. Told you I was being slow :) that makes perfect sense. Thanks, Andrew