From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 17815 invoked by alias); 2 May 2019 06:59:06 -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 17806 invoked by uid 89); 2 May 2019 06:59:06 -0000 Authentication-Results: sourceware.org; auth=none X-Spam-SWARE-Status: No, score=-1.9 required=5.0 tests=BAYES_00,SPF_PASS autolearn=ham version=3.3.1 spammy=pretest 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; Thu, 02 May 2019 06:59:04 +0000 Received: from fencepost.gnu.org ([2001:470:142:3::e]:38088) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1hM5gK-00014L-4H; Thu, 02 May 2019 02:59:01 -0400 Received: from [176.12.229.109] (port=37654 helo=[10.208.206.146]) by fencepost.gnu.org with esmtpsa (TLS1.2:RSA_AES_128_CBC_SHA1:128) (Exim 4.82) (envelope-from ) id 1hM5gB-000255-Dc; Thu, 02 May 2019 02:58:55 -0400 Date: Thu, 02 May 2019 06:59:00 -0000 User-Agent: K-9 Mail for Android In-Reply-To: <20190501195113.69aea752@f30-4.lan> References: <83wojaovbp.fsf@gnu.org> <077aee8c-7bef-bad6-a6a1-e69f116cc18b@simark.ca> <20190501195113.69aea752@f30-4.lan> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable Subject: Re: The 'cold' function attribute and GDB To: gdb-patches@sourceware.org,Kevin Buettner ,Simon Marchi From: Eli Zaretskii Message-ID: 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/msg00030.txt.bz2 On May 2, 2019 5:51:13 AM GMT+03:00, Kevin Buettner wro= te: > On Wed, 1 May 2019 16:17:04 -0400 > Simon Marchi wrote: > > Also, which commit of GDB is this with? I recall some patches > related to non-contiguous > > address ranges not too long ago. >=20 > As I recall, I committed the non-contiguous address range stuff in > late August of 2018. It might be the case that 8.3 will be the first > release to include that support. Any build based on a commit to > master since 2018-08-24 should have this support. The non-contiguous address ranges support seems to target specifically the = disassembly command? This does display 2 separate address ranges, both in = GDB 8.2 and in the latest pretest of 8.3. But were those changes supposed = to teach backtrace and stack frame reporting in general about multiple rang= es? Because in that case GDB needs to solve the inverse problem: go from t= he address to the symbol.