From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from eggs.gnu.org (eggs.gnu.org [209.51.188.92]) by sourceware.org (Postfix) with ESMTPS id AE3D93858C74 for ; Tue, 1 Feb 2022 16:41:10 +0000 (GMT) DMARC-Filter: OpenDMARC Filter v1.4.1 sourceware.org AE3D93858C74 Received: from [2001:470:142:3::e] (port=44596 helo=fencepost.gnu.org) by eggs.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1nEwDK-0001YW-I3; Tue, 01 Feb 2022 11:41:08 -0500 Received: from ip5f5a8abe.dynamic.kabel-deutschland.de ([95.90.138.190]:56534 helo=[192.168.111.41]) by fencepost.gnu.org with esmtpsa (TLS1.2:ECDHE_RSA_AES_128_GCM_SHA256:128) (Exim 4.90_1) (envelope-from ) id 1nEwDB-00074w-VL; Tue, 01 Feb 2022 11:40:59 -0500 Message-ID: Date: Tue, 1 Feb 2022 17:40:54 +0100 MIME-Version: 1.0 User-Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:91.0) Gecko/20100101 Thunderbird/91.5.0 Subject: Re: [PATCH v2] gdb, btrace: improve error messages Content-Language: en-US To: Simon Marchi , Markus Metzger Cc: gdb-patches@sourceware.org References: <20220201150156.2165646-1-markus.t.metzger@intel.com> From: Simon Sobisch In-Reply-To: Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit X-Spam-Status: No, score=-2.2 required=5.0 tests=BAYES_00, DKIMWL_WL_HIGH, DKIM_SIGNED, DKIM_VALID, DKIM_VALID_AU, DKIM_VALID_EF, NICE_REPLY_A, SPF_HELO_PASS, SPF_PASS, TXREP, T_SCC_BODY_TEXT_LINE autolearn=ham autolearn_force=no version=3.4.4 X-Spam-Checker-Version: SpamAssassin 3.4.4 (2020-01-24) on server2.sourceware.org X-BeenThere: gdb-patches@sourceware.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: Gdb-patches mailing list List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 01 Feb 2022 16:41:12 -0000 Am 01.02.2022 um 16:17 schrieb Simon Marchi: > > > On 2022-02-01 10:01, Markus Metzger wrote: >> When trying to use 'record btrace' on a system that does not support it, >> the error message isn't as clear as it could be. See >> https://sourceware.org/pipermail/gdb/2022-January/049870.html. >> >> Improve the error message in a few cases. > > That looks good to me, but you might want to see if the other Simon has > some feedback. > > Simon > I like it very much, thanks to both of you!